-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jon Nelson wrote: > On Thu, 13 Apr 2006, Tim Harper wrote: ... >> That should at least upgrade all of your packges to the version of the next >> distro. I've upgraded many a times fedora core from an entire number to the >> next via yum, I don't see any reason why you couldn't do it with SUSE. > > One very good reason is that sometimes the version (and package) number > of a package between betas (or rc's) and final may not change but the > actual content may. > > What I mean is this: let's say you have a package 'foo' version 1.0, > release 1. The RPM would then be: foo-1.0-1 > > Let's say that the compiler changes between releases, and the foo > oackage gets rebuilt. Now, foo's source and packaging didn't change, so > the version and release number don't change either. However, the > contents did change.
In theory, you are absolutely correct. But in this case that won't happen, as SUSE uses an automated build process that counts up the release as soon as a new build happens (AFAICR - correct me if I'm wrong). And I'd use smart over yum any time ;) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEPsnRr3NMWliFcXcRArnvAJwPX4asoxe/sw8c0xUsvw4SD3MV/gCgi9mX c7J4OOkixfT6nj6XQfeEtbU= =Nuy0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
