Date: Wed, 1 Feb 2012 23:19:21 -0600 From: Mark Linimon <linimon@lonesome.com> To: Michael Scheidell <michael.scheidell@secnap.com> Cc: ports@freebsd.org Subject: Re: not for arch? use arch? don't care arch? Message-ID: <20120202051921.GC6434@lonesome.com> In-Reply-To: <4F296566.805@secnap.com> References: <4F296566.805@secnap.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 01, 2012 at 11:16:38AM -0500, Michael Scheidell wrote: > "The ChangeLog mentioned some sparc64 fixes, so it's worth giving it a > try again, but the port depends on boost-libs now which is marked as > broken on sparc64, so it cannot actually be tested." > > So, how do you want me to handle this? I'd say leave out the following stanza, and also leave out ONLY_FOR/ NOT_FOR_ARCHS: > -.if ${ARCH} == "sparc64" > -BROKEN= Does not compile on sparc64 > -.endif That way, if someone happens to fix boost on sparc64, pointyhat will still try to build the dependent port, and we'll find out if it builds or not. Otherwise, everyone will probably forget about it and it will never be tried. (Builds of ports which are dependent on broken ports are not attempted by pointyhat in any case.) mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120202051921.GC6434>