Date: Mon, 15 Jul 2013 08:33:39 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Devin Teske <dteske@freebsd.org> Cc: Chris Rees <crees@bayofrum.net>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Garrett Wollman <wollman@hergotha.csail.mit.edu> Subject: Re: [HEADSUP] No more pkg_install on HEAD by default Message-ID: <20130715063339.GG1516@ithaqua.etoilebsd.net> In-Reply-To: <13CA24D6AB415D428143D44749F57D7201FC59E8@ltcfiswmsgmb21> References: <13CA24D6AB415D428143D44749F57D7201FC3AA2@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3C92@ltcfiswmsgmb21> <CA%2B7WWSe7C2UXAsEX3OZH7nPJJbxotpQ_iYBxgake4R68sbUtLA@mail.gmail.com> <13CA24D6AB415D428143D44749F57D7201FC3FAA@ltcfiswmsgmb21> <CAGE5yCoH2auer_kKpUT_caFUZPpVM5TdAFH5tJcGgF4Ji12f0g@mail.gmail.com> <201307140613.r6E6Dsov002016@hergotha.csail.mit.edu> <201307140706.r6E76Kg0002959@hergotha.csail.mit.edu> <13CA24D6AB415D428143D44749F57D7201FC51FE@ltcfiswmsgmb21> <7325EE70-8821-4350-9D8A-E5CAAC548FE9@bayofrum.net> <13CA24D6AB415D428143D44749F57D7201FC59E8@ltcfiswmsgmb21>
next in thread | previous in thread | raw e-mail | index | archive | help
--nqkreNcslJAfgyzk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 14, 2013 at 04:52:26PM +0000, Teske, Devin wrote: >=20 > On Jul 14, 2013, at 8:01 AM, Chris Rees wrote: >=20 > > On 14 Jul 2013, at 08:29, Teske, Devin wrote: > >>=20 >=20 > Simple, really. >=20 > Let's take RPM for example. The RPM package format has been ported to oth= er platforms. So does pkgng ported on Linux, OS X, dragonfly, NetBSD... >=20 > But, I can't take archivers/rpm4 and build on RPM on FreeBSD and install = it on RedHat. Yes you can, I do it at work all the time, on FreeBSD I do create AIX rpms = and RedHat rpms. >=20 > This is because the RPM format records the platform that you "build" your= RPM on (not the binaries, just the RPM) *into* said RPM. So does pkgng. >=20 > This actually adds a requirement to the RPM production that the RPMs be p= roduced on the platform that they will be installed-to. No. >=20 > Currently, no such restriction exists for the building of FreeBSD package= s (within our system). This would have been true if we had ported pkg_creat= e (and may continue to be true if we ported pkg and its ilk), but let's say= for the sake of argument that the future of "pkg" looks bright and it gets= ported to all sorts of systems (ported in a fashion similar to RPM) *and* = we find one day that the +MANIFEST starts containing a target-platform (res= ulting in refusal to install a *.txz package because it was rolled on a dif= ferent platform. Thank for describing the exact situation pkg is right now. >=20 > In that case, we'd then prefer to by-pass the tools and use our own metho= d of creating the tar-ball to lift such a restriction. The restriction you are speaking about does not exists. >=20 > ASIDE: If I knew how to force rpmbuild into creating androgynous packages= for other architectures, I'd be doing that to life the restriction there t= oo, but I haven't figured out that. >=20 > Basically... within our "pkgbase" tree, we like the branch within the tre= e to dictate how a package is built... not what platform you're on. The goa= l being that we can run a single package-build host that builds all of our = packages from a single platform. You can do it with pkgng just easily, as well as you can do it with rpm. Bapt --nqkreNcslJAfgyzk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlHjl8MACgkQ8kTtMUmk6ExGPwCeL2zL58KJo1nZLNUpgam1nEeg yc8An3JN+3qqgXp8d4wA5rA1hfw76S4j =LWHv -----END PGP SIGNATURE----- --nqkreNcslJAfgyzk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130715063339.GG1516>