1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 09/15/2012 03:59 AM, Michał Górny wrote: |
5 |
> On Fri, 14 Sep 2012 19:43:42 -0400 |
6 |
> "Rick \"Zero_Chaos\" Farina" <zerochaos@g.o> wrote: |
7 |
> |
8 |
>> On 09/14/2012 05:27 PM, Michał Górny wrote: |
9 |
>>> On Fri, 14 Sep 2012 17:18:16 -0400 |
10 |
>>> "Rick \"Zero_Chaos\" Farina" <zerochaos@g.o> wrote: |
11 |
>>> |
12 |
>>>> -----BEGIN PGP SIGNED MESSAGE----- |
13 |
>>>> Hash: SHA1 |
14 |
>>>> |
15 |
>>>> On 09/14/2012 04:56 PM, Ciaran McCreesh wrote: |
16 |
>>>>> On Fri, 14 Sep 2012 16:51:54 -0400 |
17 |
>>>>> "Rick \"Zero_Chaos\" Farina" <zerochaos@g.o> wrote: |
18 |
>>>>>> I have a personal vendetta on this subject. Several eclasses set |
19 |
>>>>>> a completely worthless description (and even more set a mostly |
20 |
>>>>>> worthless DESCRIPTION) which ends up contaminating the |
21 |
>>>>>> DESCRIPTION for an ebuild when inherit is done after DESCRIPTION |
22 |
>>>>>> is set. |
23 |
>>>>> |
24 |
>>>>> http://article.gmane.org/gmane.linux.gentoo.devel/78813/ |
25 |
>>>>> |
26 |
>>>>>> I realize that most of you will find this a little pedantic, |
27 |
>>>>>> however, I find that needing to move my DESCRIPTION to below the |
28 |
>>>>>> inherit often severely affects the readability of the ebuild, and |
29 |
>>>>>> all to avoid a completely (or nearly) worthless DESCRIPTION from |
30 |
>>>>>> contaminating my environment. |
31 |
>>>>> |
32 |
>>>>> You want your inherit line to be as near as the top as possible. |
33 |
>>>>> The only things you should have before the inherit line are EAPI |
34 |
>>>>> and any variables used by eclasses to determine behaviour. |
35 |
>>>>> |
36 |
>>>>> |
37 |
>>>> I have a nasty habit of writing ebuilds to be both live and |
38 |
>>>> versioned which requires me to test ${PV} then set things like |
39 |
>>>> inherit VCS, SRC-URI, and KEYWORDS below. The large if block |
40 |
>>>> looks better in my opinion below the settings which are the same |
41 |
>>>> for all versions, rather than in the middle. |
42 |
>>>> |
43 |
>>>> Yes, it's a readability issue, but the point is, this shouldn't be |
44 |
>>>> an issue at all. |
45 |
>>> |
46 |
>>> Use unifdef. Look at my overlay, and my ebuilds in the tree. |
47 |
>>> |
48 |
>> |
49 |
>> So just so we are clear, everyone but me thinks that |
50 |
>> DESCRIPTION="Based on the ${ECLASS} eclass" is a completely useful |
51 |
>> and critically required piece of code? |
52 |
> |
53 |
> No. We agree with you that it is useless but you are saying that with |
54 |
> a *completely* wrong reasoning. |
55 |
> |
56 |
>> Until that point I'll probably keep bringing this up. |
57 |
> |
58 |
> Don't forget to threaten us that you'll leave Gentoo. |
59 |
|
60 |
While I may be completely unreasonable in my requests you will never see |
61 |
those words spoken from me. If all of you quit I'd develop gentoo |
62 |
(poorly) by myself and if I was kicked out (which I'll try to avoid) |
63 |
I'll keep developing Pentoo based on Gentoo as I have been for the last |
64 |
7 years. Please don't mistake my belly aching for a lack of dedication |
65 |
to this project, it is precisely my dedication that causes me to care so |
66 |
much. |
67 |
|
68 |
- -Zero |
69 |
> |
70 |
|
71 |
-----BEGIN PGP SIGNATURE----- |
72 |
Version: GnuPG v2.0.19 (GNU/Linux) |
73 |
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ |
74 |
|
75 |
iQIcBAEBAgAGBQJQVNM/AAoJEKXdFCfdEflKDJ0P/R5cdzIryH3KQdLEsgziBjKr |
76 |
iBZhDg5W21RzDTZYWyk8rU4I8T84PYgB2hlYteOcbYoBDAA16WXUd6mktcxowJj7 |
77 |
3TJaohedKJl+gOF7y3Ji/i4RJMtdftPfLIqNFiCI+M2UfPS7JjImU68TXtEccYHH |
78 |
q9XNnHCiZY2dWT71VJf0mIFU/aUEYwsJYLUmNFO6hjKWeItkAdYD+Z4Crz8U31dt |
79 |
CyTGa9yju0fMCr33aTIlpPKagtBJq6xKz+mHAZUqnbf54ZPam81hcDc/5T3CkfWN |
80 |
jby8rJeAlRHzVu8DHZcQR1VCpe505FMi759Uzz78cx+8hNrgbcCLEoHaGnmkePl0 |
81 |
hhqPPEZM0IEtGydT2ZNH4UdGEuGufQvsT84Ul3LyKinPoX2iUyvIo9iTroUcRVUh |
82 |
S0kS4Qiv/iSV2HAK39nM6y5Q7YRVUdzjKNS3Ia8PjPqxr4YIHVzjmj08nyiL1hPM |
83 |
VAD8tomefb91k9ZtbeHaF/+niX0Ps/skU7Kr0CXZ53B90LvnCVdZ4RjqwcvhYcoH |
84 |
ZQEAFV3oMr9vd6JIZb30fHFqGzetnOnQHchNqbffP5CBLV0/bfzem1hnXyVAwGHA |
85 |
OMsYiGtfxVYCYIdLlsc0k15BTeP3D0IqkZYLLlkQbFeeQHskDY40uyfsENw2DrP1 |
86 |
V4YqERQFubPRZgjGpqGT |
87 |
=LAXF |
88 |
-----END PGP SIGNATURE----- |