On Thu, Mar 31, 2005, Binary Crusader wrote: > Am I correct in saying that you can't use the binary packages provided > by OpenPKG.org if you build and install openpkg in your own custom > prefix (i.e. not /openpkg, but /opt/foo for example)?
Yes, you're right. > I saw a reference to openpkg-tool when someone mentioned apt-get in > the past. Currently I am partly responsible for a set of Red Hat [...] When we evaluated apt we came to the conclusion that it seems to be the perfect solution when it comes to binary packages. On the downside, support for source builds (which is the main focus of OpenPKG) hasn't looked that fine, especially when it comes to compile time options. Maybe this has changed and apt has gained in the area, but we haven't checked recently. > The reason why I ask about this at all is that it appears that > installing an OpenPKG rpm isn't as simple as 'openpkg rpm -i > http://some/url/myopenpkg.rpm' in the sense that it doesn't > automatically fetch the other packages needed to install the specified > package from the corresponding specified URL. It appears to assume > that you already have the pre-requisites for the specified package > installed. Correctly. Automatic dependency resolving is one of the most wanted features we would like to have in OpenPKG. For now, one can use the openpkg build tool but this is more or less a preliminary fix. Up to now there is no final solution on this issue but some guys are working on it. -- christoph schug <[EMAIL PROTECTED]> ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [email protected]
