On Thu, Jun 25, 2009 at 12:42:11PM +0200, Ralf Becker wrote:
I'm building rpm packages for EGroupware (www.egroupware.org). They have a "metapackage" requiring the default modules and then executing a post_install script (create database, install EGroupware and all modules via a comand line client). All modules depend of a core module, which is also required by the metapackage and which includes the post-install script itself. (That way you can use the metapackage for convenience, but you can also install the single packages, if you want to).
What I expect would be the following behaviour:
1. Install required packages (including required core package) 2. Install metapackage 3. Execute post install of metapackage
(That's eg. the behaviour of yum or aptitude).
What happens is the following:
1. Install some of the required packages 2. Install metapackage 3. Execute post install (which fails, because not all modules there) 4. Install some more required packages and core package
I dont understand the reason behind that behaviour and could not find a way around it. The required packages installed after the metapackage always changing a bit - thought the majority of the packages is installed before, but not all.
I already tried with openSUSE11.1 and SLES11: - PreReq Tag with core package name or file-name - several ways to background a helper script waiting for all files to appear in the filesystem - zypper always detects it and waits patiently for it to exit ;-) - explicitly specify the core package first on command line: zypper install egroupware-core egroupware
Any help is welcome, thanks :-)
Please attach a solver testcase, i.e. a tar of the driectory created by zypper install --debug-solver egroupware-core egroupware Thanks, 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: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org