Re: [gentoo-dev] Dynamic SLOTs

[Jason Stubbs]

On Saturday 31 July 2004 15:46, Mike Frysinger wrote:
> On Saturday 31 July 2004 12:09 am, Jason Stubbs wrote:
> > I added support for USE-based SLOTs to
> > support the third and fourth.
>
> i know this is off topic of your e-mail, but could you go more into depth
> on this ?
> CHOST / CCHOST / cross compiling dynamic SLOTs interest embedded very much

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.

A sideline issue to USE-based SLOTs is that it would be way to easy to end up 
with spaces inside the USE-reduced SLOT string. Working support for spaces 
within a single atom (for when SLOT-based deps come in), while not so 
difficult, would slow everything down - as would figuring out whether every 
non-SLOT satisfying ebuild can be configured to be satisfying actually.

<OT>
If you're asking about using portage itself to do the cross-compiling, well 
we're still a ways from that I think. Isn't the main issue there that 
packages link against / instead of ${ROOT}? I'd say portage can be changed to 
support it fairly easily, but every ebuild will need to be changed to 
configure/hack Makefiles/whatever to link against ${ROOT} instead.

To summarize the required portage features (as far as I can see):
* Define ROOT as "/" if it's not defined by the user
* Add support for an "alias" file to profiles

The "alias" file would simply hold aliases for commands. In this case, 
somebody building for an embedded device would create the file and have it 
specify which gcc they wanted and whatever else. ("alias" or something to 
that effect, btw, will probably be needed for darwin/bsd to alias things such 
as make to gmake.)
</OT>

Whichever your question was, I hope I answered it. :)

Regards,
Jason Stubbs

--
gentoo-dev@g.o mailing list