On Thu, 2009-06-11 at 21:01 -0500, Shawn Walker wrote: > Some packages provide this legacy information, and some do not. I don't > know what the logic was behind that. > > Beyond that, pkg(5) has no knowledge of the SVR4 package database and is > unable to extract SVR4 package information or manage SVR4 packages.
Right. pkgbuild uses the legacy information to map svr4 package names to pkg(5) package names. Since some packages don't include a legacy action, it should probably always look for an IPS package, too, when resolving dependencies. Jan, if you want to work on this, I think it should work as follows: - for each dependency (Requires) look for a legacy action, if not found look for an svr4 package, if not found look for an IPS package. The order is because pkginfo finds both SVr4 packages and legacy actions and IPS is last because it's slow :/ - svr4 packages should include svr4 and legacy dependencies - IPS packages should include IPS dependencies (legacy deps translated to IPS package names) - warning should be printed if a dependency is omitted because it's for a different packaging system. - BuildRequires dependencies should work with either svr4 or pkg(5) packages Laca
