You are not logged in.
Hello everyone,
first let me apologize if this has been asked before, but I couldn't find it with google and the forums search.
What would you guys (especially the devs) think of creating an additional AUR package for every daemon of interest with an -rcd suffix, that just contains an rc.d script?
For example:
cups -> cups-rcd
openssh -> openssh-rcd
These could then pull the regular package, so users who prefer the rc.d scripts may use the following command to get the official package and also get rc.d scripts:
$favoriteAurHelper -S cups-rcd openssh-rcd
Positive notes:
- We could use the already existing AUR infrastructure with all its nice features: everyone could submit an rc.d script for their favorite daemon(s), post comments with improvements/suggestions/..,
- We could use the existing AUR tools to install those packages
- It would not be necessary to repackage every daemon
Negative:
- The AUR would get a lot of new packages all over sudden
- Arch dev team might not like it (which is totally fine for me)
- No pure systemd-free Arch Linux system (but who has the time for that anyway?)
I am not saying that I have the time to get at least one box running without systemd and actually use those rc.d scripts, it's just a question that I have on my mind. And even if no one likes the idea, at least there would be a thread about it and others could read up on it.
Please do not abuse this thread to share your opinion on init systems and why any of them should be better than the others, do this on your personal blog.
Last edited by robotanarchy (2013-05-20 23:33:17)
Offline
What would you guys (especially the devs) think of creating an additional AUR package
AUR = Arch User Repository.
Core and Extra are where devs put packages.
Anyone can create AUR packages, so if you think these would be useful, submit them. There is no need for dev approval, and asking them to do it is ... I can't find just the right word for this sentence, I don't think it's *bad* per-se, but odd.
EDIT: for clarity I did not mean it wasn't good to ask. This seems like a perfectly good forum discussion topic to get input. I just wouldn't ask devs to make this for you. We as a users can make this if we are so inclined.
Last edited by Trilby (2013-05-21 00:08:40)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Why not create one package with all the daemons?
Offline
There is no need for dev approval, and asking them to do it is ... I can't find just the right word for this sentence, I don't think it's *bad* per-se, but odd.
Well I thought it was a good idea to ask/discuss it, because it wouldn't be just a few packages and systemd alternatives seem to be sort of a sensitive topic currently.
Why not create one package with all the daemons?
Why not start a collection of scripts in github like falconindy did for systemd way back when? One package, many scripts, easy.
It's easier to keep track of the changes (actually read the new rc.d scripts) and maybe easier to maintain. You could also downgrade/change single rc.d scripts in case one is broken rather than downgrading them all.
Last edited by robotanarchy (2013-05-21 00:12:34)
Offline
Why not start a collection of scripts in github like falconindy did for systemd way back when? One package, many scripts, easy.
Offline
Seems kind of pointless to maintain a "package" just for 1 file. You're instantly doubling the number of files to maintain (the rc.d script itself, plus the PKGBUILD for each rc.d script).
Just my personal opinion.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline