| 1 |
On 08/03/2017 06:33 PM, Ulrich Mueller wrote: |
| 2 |
>>>>>> On Thu, 3 Aug 2017, Michael Orlitzky wrote: |
| 3 |
> |
| 4 |
>> The developer handbook that I just said didn't mention variables in |
| 5 |
>> HOMEPAGE at all. |
| 6 |
> |
| 7 |
> It did, even back in 2004: |
| 8 |
> https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml?hideattic=0&revision=1.10&view=markup#l534 |
| 9 |
> |
| 10 |
|
| 11 |
You got me, but now we can see where that text came from and it proves |
| 12 |
my original point that the last line was added as an afterthought and |
| 13 |
isn't any sort of policy: |
| 14 |
|
| 15 |
https://bugs.gentoo.org/show_bug.cgi?id=73272 |
| 16 |
|
| 17 |
Which is good, because it's a silly rule, and hundreds of ebuilds in the |
| 18 |
tree wisely ignore it. |
| 19 |
|
| 20 |
Why single out HOMEPAGE? I might like to copy/paste the econf arguments, |
| 21 |
so should we forbid the use of $(use_enable foo) and force everyone to |
| 22 |
use "if" statements? Of course not; if you need the value of HOMEPAGE |
| 23 |
(or anything else), there are more intelligent ways to get it than |
| 24 |
opening up the ebuild, digging though the source code, and manually |
| 25 |
performing the variable substitutions that the programming language is |
| 26 |
there to do for us. |
| 27 |
|
| 28 |
Use the metadata, use eix, use emerge --search, write an echo statement |
| 29 |
into the ebuild, whatever. Don't handicap everyone so that you can treat |
| 30 |
their source code as part of your user interface. |
Archives