1 |
On Sat, 29 Mar 2008 21:16:51 -0700 |
2 |
Brian Harring <ferringb@×××××.com> wrote: |
3 |
> Contrasting tabs vs spaces is a whole other matter. One of the |
4 |
> things you attempted to do in splitting PMS was to force certain |
5 |
> technical tweaks through because frankly, they made sense (or you |
6 |
> were stubborn, and it mostly made sense). That's fine. |
7 |
|
8 |
Not where those things involve large tree changes... |
9 |
|
10 |
> Fairly obvious, the suffix0 case is pretty rarely used. |
11 |
|
12 |
It's used more than a lot of other things... Some file suffixes for |
13 |
unpack are only used by a single package, for example, yet they're |
14 |
still in there. Ditto for some of the utilities. |
15 |
|
16 |
> Quick look at the commiters behind the explict 0 suffixes, you |
17 |
> don't see any maintainer actually repeat it in another pkg- |
18 |
> personally, I suspect majority of it was new dev mistake, in some |
19 |
> cases propagated (wschlich feel free to correct me on this sine |
20 |
> you've got the most there). For dvd95, well aware pylon wasn't new |
21 |
> at that point, so theory doesn't quite hold there (although oversight |
22 |
> may fly). |
23 |
|
24 |
Doesn't follow. Most upstreams don't use versions that fit an |
25 |
unversioned part most of the time. You wouldn't expect to see it |
26 |
repeated all over the place because in the real world it's not a very |
27 |
common (but importantly, not non-existent or massively rare) issue. |
28 |
|
29 |
> > You don't want to start breaking people who use >=..._alpha0 when |
30 |
> > the version in the tree uses plain _alpha, for example. |
31 |
> |
32 |
> Explicitly requiring on disk to not specify implicit components in no |
33 |
> way breaks atom support, or anything else for that matter. Either |
34 |
> this is a minor brain fart on your part, or again, you're going to |
35 |
> have to be a fair bit more clear in your explanation. |
36 |
|
37 |
Introducing multiple sets of versioning rules is a far worse gotcha |
38 |
than a ban on duplicates. Banning _alpha etc in some places but not |
39 |
others gets very confusing very quickly. |
40 |
|
41 |
> > Package managers have to deal with this kind of thing, and it's |
42 |
> > not one of those areas where we can change reality with little or |
43 |
> > no impact. |
44 |
> |
45 |
> While package managers have to deal with this, there are two strong |
46 |
> args for forcing such a change into the repo itself; |
47 |
|
48 |
Repositories are already not allowed to contain duplicated versions. |
49 |
That's a sufficiently strong guarantee. |
50 |
|
51 |
> 2) not surprisingly, it actually simplifies manager implementation. |
52 |
> Tracking internally whether 1.0 is actually 1.0-r0 on disk or not |
53 |
> means extra level of mappings required, meaning more areas to screw |
54 |
> it up. |
55 |
|
56 |
The package manager has to deal with equality and equivalence |
57 |
separately anyway... If you're storing 1.0 when the actual version is |
58 |
1.0-r0 you have issues regardless of whether -r0 itself is banned on |
59 |
disk -- if you want to prevent that, you have to start banning versions |
60 |
like 086 and 1.00 too. |
61 |
|
62 |
-- |
63 |
Ciaran McCreesh |