Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Mar 2012 18:28:01 +0100
From:      Baptiste Daroussin <bapt@freebsd.org>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        current@freebsd.org
Subject:   Re: ABI/architecture identification for packages
Message-ID:  <20120321172801.GH9629@azathoth.lan>
In-Reply-To: <20120321155938.Horde.MHZBUZjmRSRPaezaqlsb3yA@webmail.leidinger.net>
References:  <20120319213508.GA1692@azathoth.lan> <20120320091935.GF1692@azathoth.lan> <20120320102008.GH2358@deviant.kiev.zoral.com.ua> <E05DC188-FDB3-4FA3-8931-4E6B335C07C9@cran.org.uk> <20120321143403.Horde.VhlEOJjmRSRPadjLnx7Eh8A@webmail.leidinger.net> <20120321135919.GG9629@azathoth.lan> <20120321155938.Horde.MHZBUZjmRSRPaezaqlsb3yA@webmail.leidinger.net>

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

--Yia77v5a8fyVHJSl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 21, 2012 at 03:59:38PM +0100, Alexander Leidinger wrote:
> Quoting Baptiste Daroussin <bapt@freebsd.org> (from Wed, 21 Mar 2012 =20
> 14:59:20 +0100):
>=20
> > On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
> >> Quoting Bruce Cran <bruce@cran.org.uk> (from Tue, 20 Mar 2012 =20
> >> 14:26:42 +0000):
> >>
> >> > On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
> >> >
> >> >> i386-32 and amd64-64 is weird and confusing.
> >> >>
> >> >> IMO, you should go either with x86-{32,64} names, or with i386/amd6=
4,
> >> >> not with a mix.
> >> >
> >> > Would we ever want to support something like x32 from Linux (which
> >> > might be amd64-32)?
> >> > http://www.linuxplumbersconf.org/2011/ocw/sessions/531
> >>
> >> Not related to x32, but related to the Linux keyword (yes, I'm in the
> >> wrong branch of this thread, but I don't have the root anymore):
> >>
> >> Can you please explain how the linuxulator ports (linux_base-*) fit =
=20
> >> into this?
> >>
> >> linux_base-f10 contains 32bit linux binaries, which run in the
> >> linuxulator on i386 and amd64. If someone steps up and finishes the
> >> 64bit linux emulation on amd64, we would be able to use a
> >> linux_base(32) and a linux_base64 (or however we want to name them
> >> then) on amd64 (both at the same time). The content of the packages
> >> generated on i386 can be used on amd64 (both are generated from the
> >> same linux binary RPMs and the few FreeBSD modifications are rm's,
> >> symlinks and config changes).
> >>
> >> Can you please explain and/or give examples which kind of metadata
> >> those ports would get?
> >
> > for packages currently their will be two possible chain for the abi:
> > the abi defined here or any
> >
> > any will be for scripts, data, etc.
> >
> > I was thinking about giving a multi arch possibilities for packages =20
> > for example:
> >
> > arch: ["freebsd:9:x86:32", "freebsd:9:x86:64"]
> >
> > when a package can be installed in both i386 and amd64
> >
> > and maybe in the Makefile:
> >
> > PKGARCH=3D	i386 amd64
> >
> > or
> >
> > PKGARCH=3D	x86:32 x86:64
> >
> > not decided yet
> >
> > for scripts:
> >
> > PKGARCH=3D	any
> >
> > But I haven't decided yet :)
>=20
> This means that you do not try to compute this, you want to rely on =20
> metadata from humans.
>=20
> How to you want to handle the common FreeBSD native port (has to be =20
> compiled, can be compiled without problems on all FreeBSD =20
> architectures (e.g. the "Hello World." program), the binary only works =
=20
> on the architecture it was compiled for)? I assume you do not want to =20
> add PKGARCH=3D$(NATIVE_ARCH) to every port. Maybe =20
> PKGARCH?=3D$(NATIVE_ARCH) in bsd.port.mk?

well is pkgarch isn't defined pkgng will fall back on the system one, so yo=
u do
not need to add it in bsd.port.mk neither in the port Makefile

regards,
Bapt

--Yia77v5a8fyVHJSl
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAk9qD6EACgkQ8kTtMUmk6EyJiACgnQVwfANJKsDWuqrkWDVmMcEl
m4kAnAkaVi/GzhDqTD7mmJS+o4bwAD9N
=cG6N
-----END PGP SIGNATURE-----

--Yia77v5a8fyVHJSl--



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