Re: [gentoo-catalyst] libxml2 python and gnome-doc-utils

[Nelson Batalha]

Thank you, I've added the warning to the gentoo wiki. Btw, awesome tool ;)

I don't know python, but I'm just curious why doesn't catalyst, in this 
stage, just export variables like $target/use to their default locations 
like make.conf and use portage as normal? (therefore correcting this issue) 
(just asking, not suggesting :P).

What else is it doing at this stage other then exporting variables and call 
emerge, that requires this change in portage? Wouldn't catalyst and the 
livecd's be easier to maintain like this?

Cheers


>From: Chris Gianelloni <wolf31o2@g.o>
>Reply-To: gentoo-catalyst@l.g.o
>To: gentoo-catalyst@l.g.o
>Subject: Re: [gentoo-catalyst] libxml2 python and gnome-doc-utils
>Date: Wed, 28 Mar 2007 11:46:00 -0400
>
>On Wed, 2007-03-28 at 12:45 +0000, Nelson Batalha wrote:
> > On the package.use I explicitly used dev-libs/libxml2 python
>
>Well, package.use doesn't work how you think it should in catalyst.
>It's a known bug, but one that won't likely be fixed for some time.
>Basically, if you use $target/use, then it will ignore package.use
>settings.  You should only use package.use when deviating from the
>profile defaults for a package, not when setting your own USE.  You'll
>need to set python globally.
>
>--
>Chris Gianelloni
>Release Engineering Strategic Lead
>Alpha/AMD64/x86 Architecture Teams
>Games Developer/Council Member/Foundation Trustee
>Gentoo Foundation


><< signature.asc >>

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

-- 
gentoo-catalyst@g.o mailing list