14 Oct
2022
14 Oct
'22
10:09 a.m.
I hope the APL playing today will work fine. Sounds like all should be
good anyway. But I realized one thing below that I maybe should comment on.
On 2022-10-11 16:38, Dave McGuire wrote:
On 10/11/22 10:31, Johnny Billquist wrote:
This is sortof a shortcoming in RPM right now, that have been brought up
by someone else as well. At the moment RPM itself have no idea about
constraints. Basically, packages might require FPP, or supervisor mode,
or whatever. But I don't have a way of tracking such requirements, or
possibly have different variants/alternatives for different hardware or
OS features. This seems like something that maybe would be good.
I've basically just started from the assumption that I only target full
fledged RSX-11M-PLUS V4 (or later), on hardware that have FPP as well as
supervisor mode.
This is probably helpful to make more clear to people, and maybe I
should think about/fix that the system can be used also if you have some
special hardware requirements/limitations.
Another thing around RPM is that at the moment, having packages from
multiple repositories are a bit tricky, and creating packages are not
very documented as well. I don't know how many people actually use RPM,
and I don't know what issues there might be.
I'm happy when I hear people finding it useful, but I mostly fix things
because of/when I have specific needs of my own that I need to get fixed.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Also, I have created an RPM package for APL,
which you can just
install if you have that thing running. But that requires FPP as well.
Yes, that's how I started. I have your (wonderful) RPM system
running on all of the networked RSX machines both at LSSM and at home.
When I saw APL in the list of available packages, I thought "Oh, easy!"
...but the executable crashes due to its FPP requirement.