Date: Fri, 20 Jan 2012 10:20:05 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Chris Rees <utisoft@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: with the cvs history? trying to help INDEX builds. Message-ID: <4F193FD5.8070208@infracaninophile.co.uk> In-Reply-To: <CADLo83-WtVmyGHM=O4FbTNbDy9h=A1t111bP6eYc%2BTL8-RGmuA@mail.gmail.com> References: <4F177264.3090708@freebsd.org> <4F17DB1C.6080503@infracaninophile.co.uk> <CADLo83-WtVmyGHM=O4FbTNbDy9h=A1t111bP6eYc%2BTL8-RGmuA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0EB61BEE0B1BACF91B7D0536
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 20/01/2012 09:18, Chris Rees wrote:
> On 19 Jan 2012 08:58, "Matthew Seaman" <m.seaman@infracaninophile.co.uk=
>
> wrote:
>> On 19/01/2012 01:31, Michael Scheidell wrote:
>>> anyway, worth the cycles?
>>> take out -.include <bsd.port.pre.mk>; -.if ${ARCH} =3D=3D "sparc64"
>>> -BROKEN=3D Does not install on sparc64
>>> -.endif
>>> and replace it with NOT_FOR_ARCHS=3D sparc64 ?
>> I'd say worth it to standardize on NOT_FOR_ARCHS / ONLY_FOR_ARCHS to
>> handle this sort of thing. By my calculations there are 28 ports that=
>> set 'BROKEN' because of architecture incompatibility on my amd64
>> system[*], whereas there are 904 ports that set either ONLY_FOR_ARCHS =
or
>> NOT_FOR_ARCHS.
> No, it's not worth it :)
>=20
> This means we won't be able to differentiate between BROKEN and IGNORE.=
Not even if people make use of the {NOT,ONLY}_FOR_ARCHS_REASON or
{NOT,ONLY}_FOR_ARCHS_REASON_${ARCH} variables?
Actually I take your point, that it should be possible to distinguish
between ports that permanently won't work on some architectures by
design, and ports that temporarily don't work because of mistakes or
broken dependencies or so forth, and that are expected to be fixed
sooner rather than later. Unfortunately those two cases are already
pretty confused. For instance (arbitrarily picking out a few grep hits):=
=2E/audio/amarok-kde4/Makefile:NOT_FOR_ARCHS_REASON_sparc64=3D "GCC-relat=
ed
build error"
=2E/audio/openal/Makefile:NOT_FOR_ARCHS_REASON_ia64=3D does not compile
=2E/biology/migrate/Makefile:ONLY_FOR_ARCHS_REASON=3D Does not compile
Where 'does not compile' or 'fails to install' are similarly the most
popular reasons given for arch-related brokenness using the BROKEN
variable. Given the banal and uninformative nature of such reasons,
there's no easy way to tell if this is a temporary condition or not.
Hmm... Perhaps if there was a BROKEN_FOR_ARCH{,_REASON{,${ARCH}}} set of
variables documented alongside the other ..FOR_ARCH variables?
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig0EB61BEE0B1BACF91B7D0536
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8ZP9wACgkQ8Mjk52CukIy6cQCeOAa/ma4VAY1jMNduJFUn4H92
WwMAn2A5QDVMBkvwL48hOp3AAyJHAuld
=Vq7y
-----END PGP SIGNATURE-----
--------------enig0EB61BEE0B1BACF91B7D0536--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F193FD5.8070208>