Date: Fri, 14 Dec 2007 15:27:10 -0500 From: "Aryeh M. Friedman" <aryeh.friedman@gmail.com> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-ports@freebsd.org Subject: Re: Limitations of Ports System Message-ID: <4762E71E.4040403@gmail.com> In-Reply-To: <20071214121906.1241dcdd@gumby.homeunix.com.> References: <475F7390.9090509@gmail.com> <0F330142-A3CA-4E6E-84BD-FDE55A8E3AEE@yahoo.com> <20071213111050.O6078@wonkity.com> <200712140312.47837.danny@ricin.com> <4761F9E2.7090706@gmail.com> <20071214121906.1241dcdd@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 RW wrote: > On Thu, 13 Dec 2007 22:34:58 -0500 "Aryeh M. Friedman" > <aryeh.friedman@gmail.com> wrote: > >> Namely if I build abc with options 123 and 345 and def with 345 >> and 678 then 345 will be cached for def since we already set it >> for abc. > > How do you know the user wants 345 set on both ports? > > It might be a useful stable feature on "abc", but causes lock-ups > on "def" There are multiple ways to handle the effects of 345 on def... only one of them is to automatically apply it the other two are def can ignore it by default or make it suer settable -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYucdzIOMjAek4JIRAgBQAJ9NZEM3EoOieFprT+f4LUe/g3GqiQCfT7N6 lW3o2lmL+g5FZk0oUsSZpxA= =nzu2 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4762E71E.4040403>