1 |
>>>>> On Sun, 23 Sep 2012, Micha³ Górny wrote: |
2 |
|
3 |
>> > \section{Restrictions upon Names} |
4 |
>> > |
5 |
>> > -No name may be empty. Package managers must not impose fixed upper boundaries upon the length of any |
6 |
>> > -name. A package manager should indicate or reject any name that is invalid according to these rules. |
7 |
>> > +No name may be empty. Package managers must not impose fixed upper |
8 |
>> > +boundaries upon the length of any name. A package manager should |
9 |
>> > +indicate or reject any name that is invalid according to these rules. |
10 |
>> > +Package managers are allowed to accept names not following those rules. |
11 |
|
12 |
[Restored proper line breaks, for readability.] |
13 |
|
14 |
>> "Here's some rules. You must abide by them. Or you can ignore them." |
15 |
|
16 |
The existing spec only says "a package manager should indicate or |
17 |
reject any name that is invalid". So it is sufficient if the PM emits |
18 |
a warning, even with the current spec. |
19 |
|
20 |
> That's wording ulm suggested, |
21 |
|
22 |
Huh, where? All the wording is yours. (On IRC I had only quoted one |
23 |
sentence from your previous pastebin.) |
24 |
|
25 |
> mine was more liberal. |
26 |
|
27 |
> The idea is that it is enough to *warn* about them but if package |
28 |
> manager *can* handle them, it should. |
29 |
|
30 |
Which the current spec already allows. I see your patch merely as a |
31 |
clarification of it. (If such is needed is debatable. You should |
32 |
rather convince PM authors if you want them to adhere to Postel's |
33 |
Law.) |
34 |
|
35 |
>> Offhand, and frankly I'm kind of pissed I had to even do this |
36 |
>> legwork because your noisy fucking ass [...] |
37 |
|
38 |
I've stopped reading here. |
39 |
|
40 |
Ulrich |