| |||||||||||||
RPM 4.10 releasedRPM 4.10 releasedPosted May 28, 2012 11:42 UTC (Mon) by vonbrand (subscriber, #4458)In reply to: RPM 4.10 released by Jonno Parent article: RPM 4.10 released
All this mess because Debian users are considered morons, unable to parse 2.3.4-0.rc5 as before 2.3.4-1; while they are instantly in position to understand that 2.3.4~2 comes before 2.3.4-1. All justified because somebody somewhen could perhaps reuse the same source file. Paint me totally unimpressed by this "technical" advantage.
(Log in to post comments)
RPM 4.10 released Posted May 28, 2012 14:29 UTC (Mon) by foom (subscriber, #14868) [Link]
Can everyone please calm down? This seems to have degenerated into a "Deb rulez!!!" "No, RPM is the bestest!!!" argument, and it's completely ridiculous.
RPM 4.10 released Posted May 28, 2012 23:45 UTC (Mon) by drag (subscriber, #31333) [Link]
Don't worry about it. It just makes it easier to know which people to ignore.
It's the internet. It is what it is.
RPM 4.10 released Posted May 28, 2012 14:48 UTC (Mon) by jamesh (guest, #1159) [Link] Well, I described a technical reason for the Debian behaviour in a parent post. If I have a foo_2.3.4-0.rc5 package, its corresponding source package would consist of the files: foo_2.3.4-0.rc5.dsc foo_2.3.4-0.rc5.diff.gz foo_2.3.4.orig.tar.gz If I have a foo_2.3.4-1 package, its corresponding source package would consist of the following files: foo_2.3.4-1.dsc foo_2.3.4-1.diff.gz foo_2.3.4.orig.tar.gz If the two packages were built off of different pristine source tarballs, then they could not co-exist in the same package archive since they depend on different contents for foo_2.3.4.orig.tar.gz. The fact you only need a single copy of the pristine source is great when the packages really are based off of the same tarball, but it can't handle this kind of case. For that, you need some way to represent "a version that sorts just before 2.3.4" in the upstream version component of the package version number.
RPM 4.10 released Posted May 28, 2012 20:07 UTC (Mon) by nim-nim (subscriber, #34454) [Link]
rpm separates the upstream source file name from the package versioning (you can define the source name from package metadata, but it's not a hard link), so you don't need to play games to reuse the same files
Now really the pre-version is put at the end of the rpm package version because that's the last element to sort when comparing packages (name-epoch-version-release), I suppose it could be made explicit with a new metadata field for informational version strings (sorted after name, epoch, software version, package release), but few people seem to miss it right now
|
|||||||||||||