From owner-freebsd-current@FreeBSD.ORG Mon Jul 15 06:33:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E569C90F; Mon, 15 Jul 2013 06:33:43 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 4E567B88; Mon, 15 Jul 2013 06:33:43 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id l18so9649128wgh.2 for ; Sun, 14 Jul 2013 23:33:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=KMjL5y84vLtDViaE/Zqn4XS4G7WvFCh6k6zMo3jy2fk=; b=w8vqCw/7v6MAwdtfR7L8cbjn+BdTc8QNQFqMLgOIV26anTXfiSxci4rJE/AYK/sE/N CGUNPcrhURgYcsfLYzH0E45flbOimwfKNeCsB9CBXumXZYWoGwYtZQ+EGw+BQl4Vqodn sibySkzHgyVIS/CCF2Nf+PZowq34Q7jyx87YzuuwZkZ/rl5+ROxXe273OM7ecr5QVl12 WLb8G2iEpqgxWiR2NQD+61sPhMFfnXfrlIVdNQxC4Z7IwXGft7UZMMFbSs8Aqy6VQm4k pSkW1/J6qw2mi09TPI3E03S975Zxvy/aSAJH2se5ce7nZL8wvHoaxSParKDufHzoHVkh dYZw== X-Received: by 10.180.74.232 with SMTP id x8mr7752455wiv.48.1373870022358; Sun, 14 Jul 2013 23:33:42 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id iz8sm18093302wic.3.2013.07.14.23.33.41 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 14 Jul 2013 23:33:41 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 15 Jul 2013 08:33:39 +0200 From: Baptiste Daroussin To: Devin Teske Subject: Re: [HEADSUP] No more pkg_install on HEAD by default Message-ID: <20130715063339.GG1516@ithaqua.etoilebsd.net> References: <13CA24D6AB415D428143D44749F57D7201FC3AA2@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3C92@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3FAA@ltcfiswmsgmb21> <201307140613.r6E6Dsov002016@hergotha.csail.mit.edu> <201307140706.r6E76Kg0002959@hergotha.csail.mit.edu> <13CA24D6AB415D428143D44749F57D7201FC51FE@ltcfiswmsgmb21> <7325EE70-8821-4350-9D8A-E5CAAC548FE9@bayofrum.net> <13CA24D6AB415D428143D44749F57D7201FC59E8@ltcfiswmsgmb21> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nqkreNcslJAfgyzk" Content-Disposition: inline In-Reply-To: <13CA24D6AB415D428143D44749F57D7201FC59E8@ltcfiswmsgmb21> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Chris Rees , "freebsd-current@freebsd.org" , Garrett Wollman X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 06:33:44 -0000 --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--