-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 14 Sep 2012 16:51:54 -0400 "Rick \"Zero_Chaos\" Farina" <[email protected]> wrote: > 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.
http://article.gmane.org/gmane.linux.gentoo.devel/78813/ > 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. You want your inherit line to be as near as the top as possible. The only things you should have before the inherit line are EAPI and any variables used by eclasses to determine behaviour. - -- Ciaran McCreesh -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlBTmfcACgkQ96zL6DUtXhGzDgCcCn6mOes+8eswLl58ba6CBX4v MisAoLNLzGivS6pDZHDF4YZv2poAY7K/ =/5qc -----END PGP SIGNATURE-----
