http://bugzilla.wpkg.org/show_bug.cgi?id=117 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #13 from Rainer Meier <r.meier at wpkg.org> 2008-05-10 11:05:49 --- > You are welcome not to, of course. But this is what Debian calls dependency > management and it seems to work for them. I am using only one single Debian system and up to now I never looked at such details. But for Debian package management it might be slightly different. As Debian delivers _binary_ packages it does not matter that much if a package is installed before or after the one it depends on is added. Why? Simply because after a software updated all binaries are available. So even if package A depends on package B then package A can be installed before package B (it might not run until package B is installed too but this might be accepted). For Gentoo for example it is a different story. If package B is not installed, then the compilation of package A might not be possible at all. The same applies for WPKG. If you use "includes" then it might happen that OfficeSP3 is installed before OfficeXP - which will clearly fail. As you said you can influence the order of installation by assigning priorities - but "leveling" priorities of a lot of package with various "cross-includes" might become quite hard to maintain. But I am fine with that - introducing the <include .../> syntax will allow you to do so if you wish. > I accept that we disagree about what the correct behaviour is and am happy to > replace all my "depends" tags with "includes" tags at some point in the > future. Thanks, I was not sure if it could be acceptable for you. A simple 'sed' script might help then to turn your dependencies into includes within all packages. > Can I clarify the include/depends/chains meanings? I'm a little confused so > here's what I think you mean: > > * package A depends B : package B must be installed before package A is > installed. Priorities will be over-ridden to ensure this. Yes. > * package A includes B : package B will added to the list whenever package A > is to be installed. Priorities will remain. Yes. If package A includes package B. It will simply be added to the profile at run-time. > * package A chains B : package B will be installed after package A. > Priorities will be over-ridden to ensure this. Yes. Package specified like this will be installed directly after installing the package which chained it (even before advancing to the next package within the profile definition). -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |