Date: Thu, 26 Feb 2004 12:47:28 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: "Dan Langille" <dan@langille.org> Cc: Oliver Eikemeier <eikemeier@fillmore-labs.com> Subject: Re: how to determine whether a port is a slave port? Message-ID: <xzp7jya12r3.fsf@dwp.des.no> In-Reply-To: <403CCE0E.15299.687E7E2F@localhost> (Dan Langille's message of "Wed, 25 Feb 2004 16:32:14 -0500") References: <Pine.LNX.4.44.0402240012310.27707-100000@pancho> <403CCE0E.15299.687E7E2F@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
"Dan Langille" <dan@langille.org> writes: > Yes, FreshPorts has no way of knowing that port X is a slave of port=20 > Y. Which means it has no way of knowing to refresh the slave port=20 > information when the master port is updated. > > FWIW" Some ports also do an include of the master port. IIRC, I=20 > found at least four methods used to implement slave ports. porteasy also has trouble with some master / slave relationships. Off the top of my head, www/apache2 and print/cups are amongst those it has trouble figuring out. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp7jya12r3.fsf>