[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 100347] numbering releases rpm update difficulties
From:       kuede <kurvoe () gmx ! ch>
Date:       2005-02-28 21:16:52
Message-ID: 20050228211652.17762.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=100347         




------- Additional Comments From kurvoe gmx ch  2005-02-28 22:16 -------
I'm not that expert in KDE's syntax for releases, but as far as I know for the \
current KDE 3.4 they called the "development releases" 3.3.90 etc. The first beta is \
called 3.4.0-2 (at least here on my SuSE).

I know it's a bit difficult to be accurate for all. My personal feeling is that \
calling a beta release for 1.2 1.2-beta (and perhabs a build number like in Opera) is \
more accurate but rpm (nor apt) could be convinced by me. A solution could be calling \
it 1.2.0.beta1 ...beta2 and the final: 1.2.1 (as the _first_ official release). This \
would also make it easier for the voluntary packagers to give explicit names to the \
packages.

After all it's not a severe issue like the dependency of amarok 1.2 on kdelibs < \
3.3.999. I only wanted to make you aware of the problems for SuSE users (anyhow \
germany's most used GNU/Linux distribution).

Thanks for your attention,
Kurt Voegtli (kuede)


[prev in list] [next in list] [prev in thread] [next in thread]