Hello, On Sun, 13 Jan 2008 20:24:53 -0500 Mark Loeser <[EMAIL PROTECTED]> wrote:
> What exactly do we need this system to do that we can't do now? The only interesting thing I can think of, is to expose some of the USE flags logic found in some ebuilds in a parseable fashion. I'm talking about things like (from mplayer-1.0_rc2_p24929-r2.ebuild): - Two flags are mutually exclusive: ( cdio implies !cdparanoia ) and (cdparanoia implies !cdio) - A flag makes sense only if another flag is on: !encode implies !aac This way portage will be able to inform/warn the user automatically that the set of USE flags the user has chosen really means some other thing. Something like: [ebuild R ] media-video/mplayer-1.0_rc2_p24929-r2 USE="X cdio -aac#1 -cdparanoia#2 -encode ..." #1 aac needs encode #2 cdio conflicts with cdparanoia But this logic will have to be exposed on a .ebuild level. > Is overriding the USE flag with use.local.desc sufficient and we just > need to document the current solution properly? I would say yes. Also, what would we gain switching to xml? The format as it is now is trivially parseable and human friendly. While if the data is in xml format it will be less human friendly, as well as, it will be harder to extract the information from shell scripts. Kindest regards, Yuri. -- gentoo-dev@lists.gentoo.org mailing list
