Re: [gentoo-dev] Dynamic SLOTs

[Jason Stubbs]

On Monday 02 August 2004 06:27, Martin Schlemmer wrote:
> On Sun, 2004-08-01 at 04:01, Jason Stubbs wrote:
> > On Sunday 01 August 2004 01:29, Mike Frysinger wrote:
> > > On Saturday 31 July 2004 04:32 am, Jason Stubbs wrote:
> > > > Well, the idea was that to create local USE flags of the form
> > > > cc-${ARCH}, have the gcc ebuilds use them to configure the cross
> > > > compiler and also have them control the the slot. The only real
> > > > difference to what there is now would be that portage would be able
> > > > to forecast the SLOT correctly.
> > >
> > > so the user would do USE="cc-arm" to get an arm cross compiler ?
> > >
> > > and then in the ebuild we'd have to do something like:
> > > SLOT="cc-arm? ( blah )" ?
> > > how'd would we specify a default slot ?
> >
> > SLOT="!cc-arm? ( !cc-foo? ( !cc-bar? ( !cc-baz ( defaultslot ) ) )"
>
> I really do not know why there hasn't been a '&&' and '||' logic
> added yet?  Will it really be that difficult to implement?

It would take some time to implement and then testing time and what not. The 
main reason it hasn't been done is that it doesn't add anything that can't be 
done already.

> > Terrible, no? This is gone anyway.
>
> What exactly do you mean by this?

There is no point adding complexity to SLOT (and making dep calculation 
intricate and very slow) for the benefit of four ebuilds that could be 
implemented without the use of dynamic SLOTs anyway.

As far as I know, allowing ${KV} as a SLOT was a quick hack to prevent 
previously installed kernel modules from being unmerged. It was/is a 
temporary solution until something better is found. That better solution is 
what I'm looking for here.

Regards,
Jason Stubbs

--
gentoo-dev@g.o mailing list