-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a personal vendetta on this subject. Several eclasses set a
completely worthless description (and even more set a mostly worthless
DESCRIPTION) which ends up contaminating the DESCRIPTION for an ebuild
when inherit is done after DESCRIPTION is set.

I realize that most of you will find this a little pedantic, however, I
find that needing to move my DESCRIPTION to below the inherit often
severely affects the readability of the ebuild, and all to avoid a
completely (or nearly) worthless DESCRIPTION from contaminating my
environment.

In my opinion, the text "# @DESCRIPTION" in an eclass is more than
enough for readability, and setting DESCRIPTION only serves to
contaminate the environment.  The is especially true for the following
eclasses that set the DESCRIPTION from the subject:

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"

Although these are the ones that make me the most unhappy, I see no
purpose for setting DESCRIPTION in any eclass as it really serves no
purpose to source the eclass then source the ebuild 0.01s later and
overwrite the DESCRIPTION.  Fixing this is not difficult, unlikely to
affect anything, but will help avoid one tiny little annoyance that
really looks like a relic from a time long long ago.

Thanks for the consideration

- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQU5jqAAoJEKXdFCfdEflKvwUQAJVcM5T7nZK959jrsjMGVFIE
TxSk8krDvepy1yl0PbQi6/wGVRt6QowxEgmY8pkntr49exe9dAXVHrRxnvEDVla+
UC1JY/FcLAGiE3QcemrDlb5Ld0ipCTzB24q+2wDJ4HyOeIfgKBi8ps+XwSg0jX6G
xiszyX7T5WxrUnLSWOt6/9JPkuqIVQKQMGTazNJ3arP2CCMsuR6oy4bJ3RfXrdPY
vo8nVokVna35Kj22AWKnNFWrr8fJfZITHBWGDSndKIq7VHMFOTPeXu+WinDvkl7i
ydMYr95BoljyheB1jiDlwgSeIACfR2e7qEoyY0I41sL9dzTk6xMZFcs/d8K35sOo
448D6beEc4U94mUqU7s5sLdmq1kU4fwp41oNfGcr/E/EcgfMY5LAJOpuXt5A9gk8
NLJCZDDqKGyKLj8CYk/IUTOfSHvkiFTOHzpI12E5iqenGeeSZkxDasQON3MkZvsQ
Fo2gj9p3mTvnegxZqTte0DQEC7OsIpNRODllXnB8nOLQsUtcu8tWdIvJLLv0/Btq
WvShYjQJFwZDqDJjg38lJC7xLjksGVn8o82BfetumqfvDLeOK39FdWFAj6fjMaey
8r5CyABTrZfqg+1D2ZoaVCZxDzMbrzDJPfl8/VzOedm4Xgi74lAin7jkxr2wLO5A
XyZLTvHe+qv+aVjUN0Wx
=RBrr
-----END PGP SIGNATURE-----

Reply via email to