Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Feb 2007 01:04:29 -0500
From:      Kris Kennaway <kris@obsecurity.org>
To:        Peter Jeremy <peterjeremy@optushome.com.au>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Weird "make index" behaviour
Message-ID:  <20070227060429.GA23281@xor.obsecurity.org>
In-Reply-To: <20070227054523.GY844@turion.vk2pj.dyndns.org>
References:  <20070227054523.GY844@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--lrZ03NoBR/3+SXJZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 27, 2007 at 04:45:23PM +1100, Peter Jeremy wrote:
> I recently did a 'make index' on my amd64 system, after which 'portsdb -u'
> complained:
> /var/db/ports/INDEX-6:6529:lightning-xpi-_2: _2: Not in due form: '<versi=
on>[_<revision>][,<epoch>]'.
>=20
> Looking at deskutils/lightning-xpi/Makefile, it specifies:
>  ONLY_FOR_ARCHS=3D i386 sparc64
> and only sets ARCH_PORTVERSION on those architectures.
>=20
> Taken individually, it seems reasonable that:
> 1) 'portsdb -u' would require valid port names in the INDEX
> 2) ARCH_PORTVERSION is only defined on architectures where the port can
>    be built
> 3) The INDEX file is cross-architecture and so 'make index' ignores
>    ONLY_FOR_ARCHS
>=20
> Unfortunately, taken all together, things break.
>=20
> The underlying problem is that lightning-xpi has different versions on
> i386 and sparc64 - which renders a common INDEX file impossible.

There are actually a number of these problems, it's actually not
always possible to uniformize because sometimes a port will build a
different upstream version of the software (e.g. ezm3 on amd64).

> My temporary work-around was to define ARCH_PORTVERSION anyway so portsdb
> is happy.  A real fix would be nice.

Yes, since the INDEX will still include ports that are excluded by
ONLY_FOR_ARCHS it needs to at least return a dummy value in this case.

Kris
--lrZ03NoBR/3+SXJZ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFF48nsWry0BWjoQKURAqnTAKCNmDVqZVr94Zx3EDD+UTL+dQOA+QCgiRZl
XFX3+Hy3hexPe5W01cayx1I=
=2tV8
-----END PGP SIGNATURE-----

--lrZ03NoBR/3+SXJZ--



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