On 10/13/06, Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
Except that a USE flag's state isn't metadata. It's something that comes from the profile.
The default USE flags, enabled to reflect the same results as running ./configure w/ no enable/disable flags, _is_ metadata; metadata about an individual package.
Perhaps you should look into getting Portage to allow separate profiles per repository. That'd get around the overlay issues...
Not really. The problem's not enabling the USE flags in the profile in the overlay (something that seems to work already w/ Portage), but the trouble of moving those flags across from the overlay to Portage when the package itself moves across. As the default USE flags are metadata about the package (not the profile), it makes sense to store that data in the ebuild, along with the rest of the package's metadata. Best regards, Stu -- [email protected] mailing list
