1 |
Drake Wyrm wrote: |
2 |
> Petteri R??ty <betelgeuse@g.o> wrote: |
3 |
> |
4 |
>>Petteri R??ty wrote: |
5 |
>> |
6 |
>>>R Hill wrote: |
7 |
>>> |
8 |
>>>>Daniel Ahlberg wrote: |
9 |
>>>> |
10 |
>>>>>* if ebuild installs COPYING and/or INSTALL into doc. |
11 |
>>>> |
12 |
>>>>Is this actually important? There are a hell of a lot of ebuilds that fail |
13 |
>>>>under this rule. I'd like to start filing patches for some of the packages in |
14 |
>>>>this list so I'm interested in knowing what's worth fixing and what's being |
15 |
>>>>pedantic. |
16 |
>>> |
17 |
>>>Not a blocker but just useless. Filing patches for ebuilds doing this is |
18 |
>>>greatly appreciated by at least me. |
19 |
>> |
20 |
>>https://bugs.gentoo.org/show_bug.cgi?id=113680 |
21 |
>> |
22 |
>>So is there a policy about [not] installing the COPYING or LICENSE files |
23 |
>>already? If there isn't one, I propose we make a decision about this to |
24 |
>>have uniform behaviour across the tree. |
25 |
> |
26 |
> |
27 |
> You're going to be hard-pressed to get any kind of consensus on this |
28 |
> issue. Many dev seems to feel that the license belongs there. In some |
29 |
> cases the COPYING, LICENSE, and/or INSTALL files contain, not boilerplate |
30 |
> drivel, but actually unique, useful information. |
31 |
> |
32 |
> Certainly there could be value in leaving out _yet_another_ copy of the |
33 |
> GPL and the banal INSTALL, but even that wouldn't justify a universal |
34 |
> ban on certain file names. |
35 |
> |
36 |
|
37 |
I am not out to ban certain file names. Just for example the copies of |
38 |
GPL-2 or the general INSTALL file. If the file does contain useful |
39 |
information I am all for installing it. It's just that usually the |
40 |
INSTALL file is not really useful unless you are manually installing the |
41 |
package from sources and then you will have the INSTALL file in there |
42 |
with the sources. |
43 |
|
44 |
Regards, |
45 |
Petteri |