1 |
Dan Armak ha scritto: |
2 |
|
3 |
>On Tuesday 15 March 2005 21:25, Tom Wesley wrote: |
4 |
> |
5 |
> |
6 |
>>Hey |
7 |
>> |
8 |
>>I've seen several queries regarding KDE's new split ebuilds and the |
9 |
>>version numbers used for specific packages. It seems that all of the |
10 |
>>KDE 3.4 packages have been versioned as 3.4. |
11 |
>> |
12 |
>>Should kmail, kopete etc not be using their own version numbers with the |
13 |
>>meta-packages being versioned based on the kde release number? |
14 |
>>IMO this would make more sense, especially when reading the kopete website, |
15 |
>>finding the latest version is 0.9.2 and then noticing that portage only |
16 |
>>has 3.4. |
17 |
>> |
18 |
>> |
19 |
>In my experience most KDE users have no idea offhand what the individual app |
20 |
>versions are and which versions belong to which kde.org release. They'd be |
21 |
>confused. |
22 |
> |
23 |
>If a lot of users told me I'm wrong, I guess I'd be willing to concede this |
24 |
>point... |
25 |
> |
26 |
>BTW, what do other distros use? |
27 |
> |
28 |
>Another problem is that there are a few KDE devs who are the same: they don't |
29 |
>bother to put real version numbers on their apps (and especially libs), and |
30 |
>they stay stuck at 0.0.1, or don't always receive a version number upgrade |
31 |
>when they change. I can't find an example offhand now, but I remember seeing |
32 |
>such before... |
33 |
> |
34 |
>And a third problem: it'd make it much easier for us to make a versioning/dep |
35 |
>mistake (think about updating 300 differently-schemed version numbers) |
36 |
>without noticing. |
37 |
> |
38 |
> |
39 |
> |
40 |
one question only: |
41 |
one of the point in having a splitted kde was that it make not necessary |
42 |
upgrade all kde because of a update of a single program. |
43 |
How do you can achive this mantaining all the packages at the same version? |
44 |
maybe with -r? versioning ? |
45 |
|
46 |
-- |
47 |
gentoo-dev@g.o mailing list |