Date: Wed, 26 Jan 2005 09:40:55 -0800 From: "Michael C. Shultz" <reso3w83@verizon.net> To: freebsd-questions@freebsd.org Cc: Bart Silverstrim <bsilver@chrononomicon.com> Subject: Re: portmanager loop? Message-ID: <200501260940.56128.reso3w83@verizon.net> In-Reply-To: <8F131149-6F9F-11D9-A3AB-000D9338770A@chrononomicon.com> References: <E2ABBBEA-6EE2-11D9-A5D5-000D9338770A@chrononomicon.com> <002c01c5038a$b9e28ed0$0201a8c0@SPECULUSHX1THE> <8F131149-6F9F-11D9-A3AB-000D9338770A@chrononomicon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
To keep everyone informed, here is how portmanager's looping problem
with XFree86 is going to be handled:
portmanager version 0.2.4_1
Adding "three strikes checking". When "make" is run on a port
it gets 1 strike, if it's made a second time it gets 2 strikes and a
warning will be printed, if it tries to build a 3rd time it gets marked
as ignore and no more attempts will be made to build it. At the end
of a portmanager -u run every port that was ignored and why it was
ignored is listed. This change doesn't solve the problem, but makes it
managable and I will have it posted before the day is over.
portmanager version 0.2.5
When a port has a second strike placed against it, instead of getting
its dependencies from /var/db/{portname}/+CONTENTS (which is very fast)
the port's dependencies will be retrieved by running "make
all-depends-list" in the port's directory (horribly slow) . I expect
this to be a clean fix for the looping problem but may take a few days
for codeing and testing before I can release this version.
-Mike
ps. Comments or other suggestions will be highly appreciated.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501260940.56128.reso3w83>