Guillermo Ballester Valor wrote: > Hello, Hola Guillermo > I've build new RPM packages for amsn, cvs version. They are called 'amsn_cvs' > and have some nice and new features with respect the relased 'amsn 0.94'. > Note that it is a development version. > To install 'amsn_cvs' RPMs you need uninstall 'amsn' because of some > conflicts.
If both packages conflict anyway, why do you call it "amsn_cvs" and not just "amsn" ? IMHO the best name/version scheme would be amsn-0.94_20051123-1... That way it would supersede amsn-0.94 and yet, when a new release comes out (either 0.94.1 or 0.95), the release version will supersede the CVS snapshot again. amsn-0.94 amsn-0.94_20051123 => upgrade amsn-0.94_20051205 => upgrade amsn-0.94.1 => upgrade or amsn-0.95 => upgrade as well It's a similar trick than how to handle "rc" (release candidate), "alpha" or "beta" versions, where you'd use a _0.1 (beta1), _0.2 (beta2) suffix: amsn-0.95_0.1 => 0.95 beta1 amsn-0.95_0.2 => 0.95 beta2 amsn-0.95_1.0 => 0.95 release Because if you use "rc1" or "beta1" in the version tag, it won't upgrade properly: amsn-0.95beta1 amsn-0.95beta2 => will upgrade, ok amsn-0.95 ======> won't upgrade (!) On a sidenote, could you also build and include amsn's systray plugin ? I've seen 2 or 3 people asking for amsn packages that include that. Would be nice, especially as an addon RPM (e.g. amsn-systray) ;) (and some work as well, the amsn source code is an awful mess) (and maybe we should take this thread to the opensuse-packaging list, that's why I'm cross-posting ;)) cheers -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _\_v FOSDEM 2006 -- 25+26 February 2006 in Brussels --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
