Re: installed ports dependency tree?
Robert Huff wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? Not sure what you mean about avoiding multiple rebuilds, unless you're talking about generating a list and installing all the ports on that list one at a time. I think I understand what you're asking for though. In the portmaster man page there is a process for generating a list of ports that you have installed on one system for reinstall on another. You can use that list whether you use portmaster or not, the ports system will handle the dependencies for you. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
Scot Hetzel wrote: On Sun, Feb 1, 2009 at 9:48 PM, Robert Huff roberth...@rcn.com wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portmaster sets PM_UPGRADE_DONE_FLAG in /var/db/pkg/pkgname for all ports that it has finished upgrading to prevent multiple rebuilds of a port during the upgrade run. That's not strictly accurate. During a given run portmaster keeps an internal list of what ports are up to date in a variable. The files you mentioned are generated during the use of the -r or the -f options so that if you have to interrupt that process you can go back with the -R option and avoid redoing work you've already done. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
Doug Barton wrote: Robert Huff wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? Not sure what you mean about avoiding multiple rebuilds, unless you're talking about generating a list and installing all the ports on that list one at a time. The installed ports form a dependency tree which is hopefully a direct acyclic graph (DAG). When there are cycles it is supposed to be a bug in the system. For a DAG you can always order the elements in such a way that this total order is compatible with the partial order given by the DAG. I don't remember if portmaster does that, but i am sure that portupgrade does it, an so does my pkgupgrade. Using such an order (it is not unique) one can guarantee that (barring bugs in the ports system) one can remove packages without breaking other packages or install without doing multiple rebuilds. -- Michel TALON ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
Michel Talon wrote: Doug Barton wrote: Robert Huff wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? Not sure what you mean about avoiding multiple rebuilds, unless you're talking about generating a list and installing all the ports on that list one at a time. The installed ports form a dependency tree which is hopefully a direct acyclic graph (DAG). Hopefully, yes. :) You answered the question for a general context, I was asking specifically what the OP was trying to accomplish. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
Randy Pratt writes: Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portupgrade installs several pkg_* tools [1]. The pkg_glob and pkg_sort tools might be what you're looking for. Here's an example: pkg_glob [package names] | pkg_sort pkg_sort seems to be the droid I'm looking for. Thanks. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
On Sun, 1 Feb 2009 22:48:37 -0500 Robert Huff roberth...@rcn.com wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portupgrade installs several pkg_* tools [1]. The pkg_glob and pkg_sort tools might be what you're looking for. Here's an example: pkg_glob [package names] | pkg_sort This produces a list for update order. The man pages are quite helpful for the pkg_* tools. HTH, Randy [1] Run pkg_info -L portupgrade-\* to see the complete packing list for portupgrade. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
installed ports dependency tree?
Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
On Sun, Feb 1, 2009 at 9:48 PM, Robert Huff roberth...@rcn.com wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portmaster sets PM_UPGRADE_DONE_FLAG in /var/db/pkg/pkgname for all ports that it has finished upgrading to prevent multiple rebuilds of a port during the upgrade run. Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
