1 |
On Saturday 19 September 2009 22:45:15 Ciaran McCreesh wrote: |
2 |
> On Sat, 19 Sep 2009 22:34:39 +0200 |
3 |
> > > The second says that the package manager mustn't treat empty |
4 |
> > > categories and categories that don't exist differently. |
5 |
> > |
6 |
> > Not quite. What it says is that an empty and a non-existing category |
7 |
> > are equivalent, which doesn't explain how to treat them. Your current |
8 |
> > interpretation is already a large improvement. |
9 |
> |
10 |
> The wording in PMS is sound, and says exactly what it needs to say. If |
11 |
> you'd like to propose clarifications to that wording that make it |
12 |
> easier to understand, feel free to do so, but the actual meaning |
13 |
> mustn't be changed. |
14 |
|
15 |
"A packager manager should not treat empty categories and categories that |
16 |
don't exist differently. Both cases should not be treated as errors." |
17 |
|
18 |
How's that? It's not circular and quite readable. And if you noticed I |
19 |
borrowed most of your interpretation. |
20 |
|
21 |
|
22 |
> >, second one is a tautology. |
23 |
> |
24 |
> It's not. It would be quite possible to write an implementation that |
25 |
> treats categories that don't exist as an error rather than an empty |
26 |
> category. We have to forbid such an implementation. |
27 |
Then say so. |
28 |
|
29 |
> If that 900 line diff is 'drop kdebuild', I suggest you don't bother. |
30 |
Stop giving me ideas! That would be a rather sane change, as there's lots of |
31 |
cruft that was explicitly denied by council in it. Also makes editing a bit |
32 |
easier ... |
33 |
|
34 |
> In |
35 |
> any case, please learn how to use 'git rebase' and only send patches |
36 |
> that are against current master -- even for patches that do apply, if |
37 |
> you're basing them upon unpublished changes, we can't use three way |
38 |
> merges when applying them. |
39 |
Ah, that sucks. Is there any non-hellish way to use git then? |