On 07/12/03 Norberto BENSA wrote:
> Marius Mauch wrote:
> > On Fri, 11 Jul 2003 18:05:45 -0300 Norberto BENSA wrote:
> > > Hello,
> > >
> > > This is a question to devs. Why does baselayout depends on
> > > sysvinit 2.84? Why is it a HARD depend? I mean, why there's no a
> > > separated sysvinit ebuild?
> > >
> >
> > Why do you think that sysvinit is a dependency of baselayout? I've
> > checked all 3 ebuilds for baselayout (1.8.5.9, 1.8.6.7, 1.8.6.8-r1)
> > in my tree and none has sysvinit as a dependency, neither does it
> > show up in "emerge -ep baselayout".
> >
>
> Read the source ;-) Look inside baselayout 1.8.6.8-r1 ebuild
>
> # SysvInit version
> SVIV="2.84"
>
> S2="${WORKDIR}/sysvinit-${SVIV}/src"
>
> src_unpack() {
>
> unpack sysvinit-${SVIV}.tar.gz
>
>
> There must be a reason I'm overlooking. There used to be a separate
> ebuild for sysvinit, but now it's included inside baselayout, why?
> Why? Why? (That's it, if you don't mind me ask :-)
Ok, but that's not a dependency. Gentoo still uses /sbin/init and
/etc/inittab for booting, I guess that's the whole reason. You see this
if you read src_install() :-P If you're going to write a /sbin/init that
uses the gentoo runlevel style nobody would stop you, but until then
/sbin/init from sysvinit will do the job.
Marius
--
[EMAIL PROTECTED] mailing list
