-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I guess I have to ask why all this is of such burning importance...
One could look at the package list and see version changes for instance. This has implications if one is using a 3rd party program they may rely on a specific package version, that may be broken or nonfunctional with a newer package or set of libs. The converse may be the case wherein someone whats to use a program but has had to hunt down a lib or whatever in order to use the package they want. I this case if they prefer to do clean installs and then fold in backed up data they need to know whether or not the lib/package they use has to be reinstalled with this version or if it is included with the new distro. Also, let's take a look a packages like xine and mplayer. In the U.S. the versions that were included were crippled because of concerns about copyright (gotta love the RIAA/MPAA) and DMA, yada yada (bleh). Comparing the version is needed to see if this is a newer version of xine/mplayer and if it has been crippled or not? Is it a newer version that will overwrite the present version the users has installed and will result in a crippled program again? This would include the gcc version, glibs, etc. So this information is value emensely by those in the community and helps those running networks on small, medium, large, or SOHO, or whatever to determine the proper upgrade paths and what to load or not. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/jcygiqnGhdjCOJsRAnvLAJ4hLMHMe7Gyep2THKPChx0fLnF/dACeL/c+ rJ5LpShA8L3pqxYDSELASRI= =zMCS -----END PGP SIGNATURE-----