Hi, bug 264685 (Get rid of package locks in package manager) asks for reasoning of and better concepts for locking packages in the package manager.
This mail should be a kickoff to define a common understanding and concept for package locks. Package locks try to provide a solution for the following use-cases 1. Distribution upgrade with 3rd party packages Desktop user Joe has purchased a full featured version of the FooBar application from vendor ACME for openSUSE 10.2 The new openSUSE 10.3 distribution contains a free version of FooBar, based on open source, built in autobuild with vendor 'openSUSE', with limited functionality. Upgrade of the distribution replaces the full featured version with the limited one. 2. Maintenance upgrade of 3rd party packages Multimedia junkie Susan likes to listen to mp3 encoded music files and regularly watches DVD movies on her laptop. Because of license issues, she installed mplayer from a 3rd party repository, including a full set of patented codec implementations. The openSUSE project provides a maintenance update for mplayer, fixing a critical security bug. This update replaces the installed mplayer, resulting in a version with limited functionality. The current solution to the above scenarious is to group packages based on their vendor attribute. Packages from unknown vendors are auto-protected in order to prevent unwanted replacements. This is a very effective but also very limited solution. Proposals anyone ? Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
