http://bugzilla.wpkg.org/show_bug.cgi?id=144 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.meier at wpkg.org --- Comment #1 from Rainer Meier <r.meier at wpkg.org> 2009-02-13 10:53:29 --- WPKG already supports dependencies. If the order of installing packages matters (in your example the admin wants to install a before b, so b seems to depend on a) an admin might specify a dependency to a on package b. This will make sure WPKG installs a before b (even if b has higher priority). I am currently not fully sure but the priority of a package is supposed to be an optional value and defaults to 0 I think. So you could for sure omit all priority definitions and build up an entirely dependency-bysed package database. Personally I set all priorities to 50 since I am using WPKG_WEB (which enforces me to enter some priority). Dependencies between package are specified by dependency definition. So I actually do not care at all about the order in which the packages are applied (at least not by priority). If a package depends on another one this should be reflected through a dependency specification in the package definition. It's true that the current implementation is verifying the installed packages in order of their local priority. This is correct from my point of view since the priority applies to the version currently installed on local machine. So I strongly recommend to specify a dependency if some packages depend on some others. That's what the dependency mechanism is for. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |