[opensuse-factory] new subpackages in virtualbox-ose package
Hi all, I created for virtualbox-ose package three new subpackages : python-virtualbox-ose,virtualbox-ose-devel and virtualbox-ose-qt see bug report from Vincent: https://bugzilla.novell.com/show_bug.cgi?id=636858 - so now if you want to use vboxgtk (GUI interface written in python+GTK) you don't have to install qt dependent part (use zypper addlock virtualbox-ose-qt in this case) as I don't want to confuse users,and I suppose they expect QT interface after installation of virtualbox-ose package, so as a dependency between virtualbox-ose and virtualbox-ose-qt I used "Recommends" keyword (this should handle also update from 11.3 to 11.4): Name: virtualbox-ose ... Recommends: %{name}-qt = %version ... So by default virtualbox-ose installation will trigger also installation of virtualbox-ose-qt .... If someone comes with better idea how to split qt subpackage without confusing users I would be glad :) you could find modified package in Virtualization repo bye Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Sep 08, 2010 at 11:09:50PM +0200, Michal ??ebe?? wrote:
I created for virtualbox-ose package three new subpackages : python-virtualbox-ose,virtualbox-ose-devel and virtualbox-ose-qt see bug report from Vincent: https://bugzilla.novell.com/show_bug.cgi?id=636858 - so now if you want to use vboxgtk (GUI interface written in python+GTK) you don't have to install qt dependent part (use zypper addlock virtualbox-ose-qt in this case) as I don't want to confuse users,and I suppose they expect QT interface after installation of virtualbox-ose package, so as a dependency between virtualbox-ose and virtualbox-ose-qt I used "Recommends" keyword (this should handle also update from 11.3 to 11.4): Name: virtualbox-ose ... Recommends: %{name}-qt = %version ... So by default virtualbox-ose installation will trigger also installation of virtualbox-ose-qt .... If someone comes with better idea how to split qt subpackage without confusing users I would be glad :)
Don't we have "split-provides" for this case? See: http://en.opensuse.org/openSUSE:Upgrade_dependencies_explanation#Splitting_a... Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le jeudi 09 septembre 2010, à 12:19 +0200, Michael Schroeder a écrit :
On Wed, Sep 08, 2010 at 11:09:50PM +0200, Michal ??ebe?? wrote:
If someone comes with better idea how to split qt subpackage without confusing users I would be glad :)
Don't we have "split-provides" for this case? See: http://en.opensuse.org/openSUSE:Upgrade_dependencies_explanation#Splitting_a...
My understanding of this (after quickly reading it) is that it helps for upgrades. But it doesn't really help when a user installs the package for the first time, does it? I think that would be the main issue Michal wants to fix here. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Sep 9, 2010 at 2:56 PM, Vincent Untz <vuntz@opensuse.org> wrote:
Le jeudi 09 septembre 2010, à 12:19 +0200, Michael Schroeder a écrit :
On Wed, Sep 08, 2010 at 11:09:50PM +0200, Michal ??ebe?? wrote:
If someone comes with better idea how to split qt subpackage without confusing users I would be glad :)
Don't we have "split-provides" for this case? See: http://en.opensuse.org/openSUSE:Upgrade_dependencies_explanation#Splitting_a...
My understanding of this (after quickly reading it) is that it helps for upgrades. But it doesn't really help when a user installs the package for the first time, does it? I think that would be the main issue Michal wants to fix here. yes exactly, currently if user install virtualbox-ose package for the first time he expect fully working virtualbox with qt gui and I don't want to break this so if user want to install virtualbox-ose and he doesn't care about qt/gtk dependency he could install virtualbox package as before: zypper in virtualbox-ose but if he doesn't want to install all qt libraries (in case of pure Gnome installation) which are needed by virtualbox-ose-qt he could use zypper addblock: zypper addlock virtualbox-ose-qt zypper in virtualbox-ose and install vboxgtk packaged by Vincent
michal
Vincent
-- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 09/10/2010 at 11:50 AM, Michal Šebeň<mseben@gmail.com> wrote: yes exactly, currently if user install virtualbox-ose package for the first time he expect fully working virtualbox with qt gui and I don't want to break this so if user want to install virtualbox-ose and he doesn't care about qt/gtk dependency he could install virtualbox package as before: zypper in virtualbox-ose but if he doesn't want to install all qt libraries (in case of pure Gnome installation) which are needed by virtualbox-ose-qt he could use zypper addblock: zypper addlock virtualbox-ose-qt zypper in virtualbox-ose and install vboxgtk packaged by Vincent
what about a virtual symbol which we require here? Requires (or Recommends?) virtualbox-gui this could be provided by -qt and vboxgtk, and the 'solver' is getting what has less transactions (IIRC). Thus on a Qr system it will prefer the -qt version, otherwise the Gtk version. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Dominique Leuenberger -
Michael Schroeder -
Michal Šebeň -
Vincent Untz