I have another minor issue with pkgng: Say package foo-1.0 depends on bar-1.0. Then bar-1.0 is upgraded to version 1.1.
So a new package bar-1.1 is built (from the port), and replaces bar-1.0 in the repository. The repository database is then updated using 'pkg repo'. Now the repository database is out of whack: It still thinks foo-1.0 depends on bar-1.0 (the deps table in the compressed repo.sqlite database - i.e. repo.txz in the repository). Admittedly the packages will still install (from the repository in question) on another machine, but nevertheless it doesn't seem quite right. One workaround is to re-create the foo package (plus any others depending on bar) and refresh the repository, but is this an omission? _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
