I propose to split baselayout Reproducible: Always Steps to Reproduce: 1. 2. 3.
I propose to split baselayout into three packages: 1. baselayout. 2. initscripts ( gentoo-sysv initscripts ). 2. SysV init.
Why?
There's no point to this. Please re-open if you can offer a detailed and persuasive explanation.
I always wondered why there's no separated sysvinit package (actually there is, but it's masked.)
1. I think, this is common practice in linux distributions. 2. This is more flexible for support (z.B. for patches). 3. More simple to change initstyle.
1. so what, we're Gentoo, not other distro's 2. i dont see how 3. not really considering every package in Gentoo that supports 'init' comes with a 'Gentoo' init script and not 'some other init script'
No one asnwered #4; what's the reason why sysvinit isn't a separated package?
I'll reopen this bug and consider it. Dmitry has some good points, in particular I think it would be easier to maintain sysvinit if it were a separate package (which Norberto pointed out exists, though it's package-masked). At the moment the sysvinit in baselayout is older than the released version according to freshmeat, and updating is a pain because I have to suck the sources into the rc-scripts cvs. I might not get to this immediately but I'll discuss it with Azarah and Spanky.
Re comment #8 I'd also welcome this change.. Perhaps splitting baselayout into it's 3 parts. 1) base (standard dirs and device nods/MAKEDEV) 2) sysvinit (user can use any init he/she wishes minit/busybox init/etc..) 3) rc-scripts (just the init scripts /etc/{init,conf}.d/ /etc/rc)
ok, baselayout is split from sysvinit now in baselayout-1.10.1-r1 and sysvinit-2.84 (which is unmasked). test and report bugs...
what about splitting rc-scripts? after all, it was the need to bump rc-scripts that often forced baselayout upgrades and caused annoying updates of device nodes and core files, which is what we are trying to avoid in first place. BTW: the part in baselayout-1.10.1-r1.ebuild that executes 'sbin.init U' should be moved to the sysvinit ebuild.
Ok, I'll reopen and consider. "annoying updates of device nodes and core files, which is what we are trying to avoid in first place" What's annoying about them?
the only thing i can think of is /etc/{fstab,passwd,group} ... all my machines use dynamic /dev (as do most people) so i dont think that's really an issue for the majority of users
> /etc/{fstab,passwd,group} ... yes, i was thinking of those. About devices, the main issue is the time to run MAKEDEV, I agree there's no risk in recreating device nodes. Thanks for considering.
Gregorio, I added fstab and group to the list of files whose ._cfg* entries are deleted automatically to ease your frustration. Regarding the device nodes, they are only created if you don't have /lib/udev-state/devices.tar.bz2 already on your system. I moved this stuff into pkg_postinst so it doesn't have to do dirty ${ROOT} tricks in src_install This is in baselayout-1.10.1-r2. I prototyped splitting into a separate rc-scripts ebuild. It was a hairy process and I don't think it's worthwhile considering the changes I've now made. Likely the split would lead to more maintainence than the current baselayout+rc-scripts setup. Resolving FIXED since Gregorio's concerns should be met now.
I'm fine with this solution, thanks a lot!
