On Mon, Jun 19, 2006 at 05:10:21PM +0200, [EMAIL PROTECTED] wrote: > Or, the other solution, would be enable pkg_add -ui (maybe with another > argument to use Ports) using the Port-system to update.
The interface will use PKG_PATH. After all, using ports is just another kind of url, similar to ftp/scp. Unfortunately, this needs an almost complete rewrite/redesign of the way package lookups and package repositories are handled in the current tools. If you want, you can look at what's going on yourself, look in the package tools, around the PackageLocator.pm file and the PackageRepository stuff. You'll notice finding packages is not as generic as it should be (there should be a generic `search object', so that you can locate packages by stem, or by package path, or some other combinations), and the current way to look up packages does things the wrong way (looks in every repository instead of stopping at the first one that holds reasonable candidates)... and there's even some completely non-functional scaffolding to go build packages from the ports tree. Hey, if it was 4 hours of work, it would already be in the ports tree. The other way around (FETCH_PACKAGES) has been functional since the last ports hackathon thanks to nikolay, and there were already quite a few minor issues to solve to make it work correctly (partial downloads did tend to stick around in the package cache). As far as building and replacing in source goes, we do know we actually need to replace libtool with something that works, and doesn't go looking in /usr/local all the time (obnoxious twit), but again, this is not a 4 hours endeavor...
