-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/15/2012 03:59 AM, Michał Górny wrote: > On Fri, 14 Sep 2012 19:43:42 -0400 > "Rick \"Zero_Chaos\" Farina" <[email protected]> wrote: > >> On 09/14/2012 05:27 PM, Michał Górny wrote: >>> On Fri, 14 Sep 2012 17:18:16 -0400 >>> "Rick \"Zero_Chaos\" Farina" <[email protected]> wrote: >>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> On 09/14/2012 04:56 PM, Ciaran McCreesh wrote: >>>>> 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. >>>>> >>>>> >>>> I have a nasty habit of writing ebuilds to be both live and >>>> versioned which requires me to test ${PV} then set things like >>>> inherit VCS, SRC-URI, and KEYWORDS below. The large if block >>>> looks better in my opinion below the settings which are the same >>>> for all versions, rather than in the middle. >>>> >>>> Yes, it's a readability issue, but the point is, this shouldn't be >>>> an issue at all. >>> >>> Use unifdef. Look at my overlay, and my ebuilds in the tree. >>> >> >> So just so we are clear, everyone but me thinks that >> DESCRIPTION="Based on the ${ECLASS} eclass" is a completely useful >> and critically required piece of code? > > No. We agree with you that it is useless but you are saying that with > a *completely* wrong reasoning. > >> Until that point I'll probably keep bringing this up. > > Don't forget to threaten us that you'll leave Gentoo.
While I may be completely unreasonable in my requests you will never see those words spoken from me. If all of you quit I'd develop gentoo (poorly) by myself and if I was kicked out (which I'll try to avoid) I'll keep developing Pentoo based on Gentoo as I have been for the last 7 years. Please don't mistake my belly aching for a lack of dedication to this project, it is precisely my dedication that causes me to care so much. - -Zero > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQVNM/AAoJEKXdFCfdEflKDJ0P/R5cdzIryH3KQdLEsgziBjKr iBZhDg5W21RzDTZYWyk8rU4I8T84PYgB2hlYteOcbYoBDAA16WXUd6mktcxowJj7 3TJaohedKJl+gOF7y3Ji/i4RJMtdftPfLIqNFiCI+M2UfPS7JjImU68TXtEccYHH q9XNnHCiZY2dWT71VJf0mIFU/aUEYwsJYLUmNFO6hjKWeItkAdYD+Z4Crz8U31dt CyTGa9yju0fMCr33aTIlpPKagtBJq6xKz+mHAZUqnbf54ZPam81hcDc/5T3CkfWN jby8rJeAlRHzVu8DHZcQR1VCpe505FMi759Uzz78cx+8hNrgbcCLEoHaGnmkePl0 hhqPPEZM0IEtGydT2ZNH4UdGEuGufQvsT84Ul3LyKinPoX2iUyvIo9iTroUcRVUh S0kS4Qiv/iSV2HAK39nM6y5Q7YRVUdzjKNS3Ia8PjPqxr4YIHVzjmj08nyiL1hPM VAD8tomefb91k9ZtbeHaF/+niX0Ps/skU7Kr0CXZ53B90LvnCVdZ4RjqwcvhYcoH ZQEAFV3oMr9vd6JIZb30fHFqGzetnOnQHchNqbffP5CBLV0/bfzem1hnXyVAwGHA OMsYiGtfxVYCYIdLlsc0k15BTeP3D0IqkZYLLlkQbFeeQHskDY40uyfsENw2DrP1 V4YqERQFubPRZgjGpqGT =LAXF -----END PGP SIGNATURE-----
