Date: Wed, 05 Feb 2003 12:21:16 -0500 From: Greg Troxel <gdt@ir.bbn.com> To: Olivier Tharan <olive@oban.frmug.org>, freebsd-ports@FreeBSD.ORG Subject: Re: libintl.so.2/4, portupgrade and evolution breakage Message-ID: <20030205172116.C157E787@fnord.ir.bbn.com> In-Reply-To: Message from Olivier Tharan <olive@oban.frmug.org> of "Wed, 05 Feb 2003 10:51:08 %2B0100." <20030205095108.GF53198@weirdos.oban.frmug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It turns out the problem with evolution was unrelated; I had added a workaround in close() in libc_r (fd leak under an obscure condition), and mismerged it on updating. > It would be cool if portupgrade kept a database of packages whose > dependencies have been update, perhaps with an option to update those > in topological-sort order. When upgrading a package, anything that That is what the -rR options are for. The combination of portupgrade, portversion and pkgdb are very useful. portsdb and portsclean are, to a lesser extent. Sure, one can use that. But then there is a huge time when the system is building. I was thinking of a way to just update a single port (dangerous but convenient), but do bookkeeping of the ports that need rebuilding because a dependency was updated. This would enable one to preserve the -r semantics over time by later calling portupgrade on all ports on the unsafe list. Essentially, I mean to split the -r operation into multiple operations of portupgrade. It would be cool if portversion printed lines in topologically-sorted order, so that if portupgrade were called in order there would be no packages in an unsafe state. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030205172116.C157E787>