1 |
William L. Thomson Jr. wrote: |
2 |
> On Sat, 2007-03-17 at 03:11 +0100, Marius Mauch wrote: |
3 |
>> On Fri, 16 Mar 2007 18:25:17 -0400 |
4 |
>> "William L. Thomson Jr." <wltjr@g.o> wrote: |
5 |
>> |
6 |
>>> Hierarchy would be the following |
7 |
>>> |
8 |
>>> snapshot -> dev -> build -> alpha -> beta .... |
9 |
>> And that's where the problems start. As you said yourself _snapshot is |
10 |
>> something universal so it doesn't really fit anywhere in the chain. |
11 |
> |
12 |
> Yes, order wise snapshots might be quite confusing. Not sure if a well |
13 |
> defined definition would clear that up. |
14 |
> |
15 |
>> Similar for _build, it usually runs parallel to normal versioning (a |
16 |
>> release also has a build number). |
17 |
> |
18 |
> That's more something specific to say glassfish where builds are weekly |
19 |
> https://glassfish.dev.java.net/public/downloadsindex.html#Promoted_binary_builds |
20 |
> |
21 |
> With major ones being milestones, similar to Netbeans. |
22 |
> https://glassfish.dev.java.net/public/downloadsindex.html#Milestone_binary_builds |
23 |
> |
24 |
> Glassfish alone is likely to comprise of a guestimated ~20 or so |
25 |
> packages. It's Sun's formerly closed source J2EE stack for the most |
26 |
> part. Very possible could be more, formerly know as WSDP |
27 |
> http://java.sun.com/webservices/jwsdp/index.jsp |
28 |
> |
29 |
>> At best older |
30 |
>> portage versions would ignore ebuilds using these new suffixes |
31 |
>> resulting in confused users, worst case stuff starts breaking. |
32 |
>> If you want to pursue this you should get some numbers of how many |
33 |
>> packages could actually make use of these new features, it simply isn't |
34 |
>> worth thinking about it for just a handful of packages. |
35 |
|
36 |
Bleh; you have to break it at one point anyhow; you added the cvs |
37 |
suffix, no? :) |
38 |
-- |
39 |
gentoo-dev@g.o mailing list |