6c5325bf0e
1. pkg_create now has a -P argument for specifying dependencies on the command line. 2. pkg_add will honor dependencies and chain-load them automatically if it finds the required package(s) in the same directory as the package that is being loaded. For best results, install packages from a directory containing all the packages you'll possibly need (like /usr/ports/packages/all). 2 remaining flaws: 1. pkg_add looks in one place (where you were when you loaded the primary pkg) for depended packages. If you can come up with a search path scheme that's not a total hack - be my guest! 2. Recursive dependency expansion can result in the name of a dep being listed more than once. This doesn't bother pkg_add since it checks for package existance with pkg_info and will skip already-loaded packages. I don't know how/if pkg_delete handles this yet, however. I need to look into it. |
||
---|---|---|
.. | ||
add.h | ||
extract.c | ||
futil.c | ||
main.c | ||
Makefile | ||
perform.c | ||
pkg_add.1 |