Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Aug 2012 16:10:07 GMT
From:      Chris Rees <crees@freebsd.org>
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   Re: ports/170946: [patch] mark certain ports broken on ARM
Message-ID:  <201208251610.q7PGA7m1029130@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/170946; it has been noted by GNATS.

From: Chris Rees <crees@freebsd.org>
To: "Mikhail T." <mi+thun@aldan.algebra.com>
Cc: Eitan Adler <lists@eitanadler.com>, Mark Linimon <linimon@lonesome.com>, bug-followup@freebsd.org
Subject: Re: ports/170946: [patch] mark certain ports broken on ARM
Date: Sat, 25 Aug 2012 17:06:11 +0100

 [CC list trimmed a little(?!)]
 
 On 25 August 2012 16:27, Mikhail T. <mi+thun@aldan.algebra.com> wrote:
 > On 23.08.2012 21:47, Eitan Adler wrote:
 >>
 >> NOT and ONLY are meant for ports which by definition will never work
 >> another arch (think x86info).  In this case the ports are just broken.
 >
 > That's a fine distinction, that makes little sense to me -- the total number
 > of ports, which can not ever work on some architecture is, probably, a
 > couple dozen... It is also not mentioned in the Handbook
 > <http://www.freebsd.org/doc/en/books/porters-handbook/dads-noinstall.html>;
 > at all:
 >
 >  *
 >
 >    If a port should be marked IGNORE only on certain architectures,
 >    there are two other convenience variables that will automatically
 >    set IGNORE for you: ONLY_FOR_ARCHS and NOT_FOR_ARCHS. Examples:
 >
 >    ONLY_FOR_ARCHS= i386 amd64
 >    NOT_FOR_ARCHS= ia64 sparc64
 >
 >    A custom IGNORE message can be set using ONLY_FOR_ARCHS_REASON and
 >    NOT_FOR_ARCHS_REASON. Per architecture entries are possible with
 >    ONLY_FOR_ARCHS_REASON_/ARCH/ and NOT_FOR_ARCHS_REASON_/ARCH/.
 >
 > Thus, I still think, using these knobs is better -- especially, when doing
 > otherwise requires splitting bsd.ports.mk into bsd.ports.{pre,post}.mk.
 > Yours,
 
 Nope.  Note that it says that it should be marked IGNORE, not BROKEN.
 
 It's a big distinction; BROKEN means it is expected to be fixed at
 some point, IGNORE means that it is not supposed to work this way.
 
 Also, don't forget that package building runs are often done with
 TRY_BROKEN, which is very helpful when doing !intel builds.
 
 I will point out again though, that instead of pre/post.mk, the
 simpler options.mk also brings in ${ARCH}....
 
 Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208251610.q7PGA7m1029130>