On Sunday 06 October 2002 02.06, Anthony Moulen wrote:
On Saturday 05 October 2002 06:54 pm, Anders Johansson wrote:
On Sunday 06 October 2002 00.45, Anthony Moulen wrote:
And finally, these are beta upgrade packages.
WTF is an upgrade package?
What do you call an RPM that upgrades another RPM? Seems like upgrade package makes a lot of sense to me.
And exactly how does it differ from a plain regular rpm?
It isn't a patch because it is from a different minor vesion. Patches are only for changes to patch levels (3.0.1 to 3.0.2 to 3.0.3).
Not really. A patch rpm is a SuSE thing that only contains the differences between the installed version and the new one.
If they were simply installed next to the other packages and when finally released they broke the upgrade, you would be complaining 10 times worse.
What are you on about? All binaries/scripts/whatever in /opt/kde3 from 3.0.3 disappear, and get replaced by 3.1. There's absolutely no "upgrade" going on there. You may be confusing things with YOU's patch rpms. These are not patch rpms.
Tell me that if a final upgrade between 3.0.3 to 3.1 comes along that you wouldn't have a fit if the upgrade broke something? Who is going to test these packages if not beta testers? Who is going to protect the end users from a bad upgrade?
You can test this perfectly well without wiping the 3.0.3 installation.
The only upgrade here is to the things in $HOME/.kde and you can test that without blowing away the kde 3.0.3 installation. I did, when I installed from CVS. And so did every previous beta.
What do you use to login? I assume you login via KDM. Have you ever tried to upgrade KDM and have it mess up? This is an important thing for people who will later upgrade their "production" environments.
Yes, but you can test it without wiping the 3.0.3 installation.
Do you know what will happen to your third party or extra kde packages?
Yes. If they're not recompiled against kde 3.1 they will fail. It is irrelevant to this discussion. //Anders