Difference between revisions of "Package dependencies"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
m
m
Line 28: Line 28:
  
 
See also:<br />
 
See also:<br />
http://sourceforge.net/mailarchive/forum.php?thread_name=63dc64100711051447q77a9be53q3812e98576f308e9%40mail.gmail.com&forum_name=wpkg-users<br />
 
 
http://sourceforge.net/mailarchive/forum.php?thread_name=Pine.LNX.4.64.0711052304260.5639%40gath.dalton&forum_name=wpkg-users
 
http://sourceforge.net/mailarchive/forum.php?thread_name=Pine.LNX.4.64.0711052304260.5639%40gath.dalton&forum_name=wpkg-users
  
 
[[category:Documentation]]
 
[[category:Documentation]]

Revision as of 08:09, 6 November 2007

Packages can depend on each other (i.e., you have to install Firefox before installing some Firefox plugin etc.).

The format is very simple, and similar to the one used for profile dependencies:


   <package id=...>
       <depends package-id="my-package"/>
       <depends package-id="other-package"/>
       ...
   </package> 

Note that "package dependencies" are now defined differently than in 0.9.6 and 0.9.7; this previous format is not supported.


A description from wpkg-users mailing list by Dr. Frank Lee:

The 'dependancy' just adds the packages to the list, which is then 
installed in order of priority. If 'foo' depends on 'bar' being present 
for 'foo' to install properly, 'bar' ought to have a higher priority than 
'foo'.

In the example above, B should be set at a higher priority than A for 
success. (I usually have 900-999 as the priority for OS patches, 700-799 
for antivirus etc, 500-599 for 'mission critical' applications, 300-399 
for useful things and 100-199 for end-user things like office. Even 
numbered centuries are 'reserved for future expansion'...)

See also:
http://sourceforge.net/mailarchive/forum.php?thread_name=Pine.LNX.4.64.0711052304260.5639%40gath.dalton&forum_name=wpkg-users