On 15 September 2012 08:51, Rick "Zero_Chaos" Farina <[email protected]> wrote: > ozzie eclass # grep 'DESCRIPTION="Based on the ' *.eclass > cannadic.eclass:DESCRIPTION="Based on the $ECLASS eclass" > confutils.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > embassy.eclass:DESCRIPTION="Based on the $ECLASS eclass" > eutils.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > games.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > gnatbuild.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > gnuconfig.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > libtool.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > linux-mod.eclass:DESCRIPTION="Based on the $ECLASS eclass" > nsplugins.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > perl-module.eclass:DESCRIPTION="Based on the $ECLASS eclass" > qmail.eclass:DESCRIPTION="Based on the ${ECLASS} eclass" > toolchain-funcs.eclass:DESCRIPTION="Based on the ${ECLASS} eclass"
+1. There's no use cases I know of where having a description as such is useful. Either the Eclass should be able to provide a useful DESCRIPTION for each and every derived ebuild, or it should provide none at all. Maybe the Eclass has a translation from $P to $DESCRIPTION somehow that is useful, but "Based on the ECLASS eclass" is about as useful as DESCRIPTION="An EAPI $EAPI Ebuild" or just "An Ebuild", or just no description at all. If the usecase for this is "Sometimes people will want to write an ebuild and not provide a description at all, and don't care that its not useful", then it shoudn't be supported by a nasty hack in the parent eclass, Portage should instead support a missing DESCRIPTION feature. -- Kent perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" http://kent-fredric.fox.geek.nz
