On Tue, Oct 25, 2005 at 08:57:59PM +0100, Ciaran McCreesh wrote: > On Tue, 25 Oct 2005 14:51:26 -0500 Brian Harring <[EMAIL PROTECTED]> > wrote: > | portage substitutes "" when metadata keys are unset during depends > | export. Seems kind of pointless requiring an empty var > | <snip> > | to do the check > | would require mangling ebuild.sh also, which I think is kind of daft. > > Hrm. KEYWORDS.missing, LICENSE.missing, DESCRIPTION.missing and > SLOT.missing are listed in 'man repoman'.
Re-read the chunks of my original email above. The suggestion is requiring HOMEPAGE='' in ebuilds, which is daft due to the fact that ebuild.sh does not discern between an unset and empty var for exporting. All stable portage (python side) sees is empty, no special flagging of unset. The repoman checks I commented on, due to ebuild.sh not discerning between an unset env var and an empty one, are testing to see if it's empty not unset/missing. It's pointless requiring the var to be set empty in the ebuild because portage (by extension repoman) doesn't know the difference between unset and empty. Making it aware of the difference is a bit daft also imo; a package that lacks a homepage I tend to think should be flagged as a warning, regardless if the author set the HOMEPAGE var or not. ~harring
pgpUkmW1ontvK.pgp
Description: PGP signature
