From owner-freebsd-stable@FreeBSD.ORG Thu Aug 16 20:24:17 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F124106566B for ; Thu, 16 Aug 2012 20:24:17 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3648FC16 for ; Thu, 16 Aug 2012 20:24:16 +0000 (UTC) Received: from seedling.local (host86-180-66-20.range86-180.btcentralplus.com [86.180.66.20]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q7GKOC9j079851 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 16 Aug 2012 21:24:12 +0100 (BST) (envelope-from matthew@FreeBSD.org) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q7GKOC9j079851 Authentication-Results: smtp.infracaninophile.co.uk/q7GKOC9j079851; dkim=none (no signature); dkim-adsp=none X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host host86-180-66-20.range86-180.btcentralplus.com [86.180.66.20] claimed to be seedling.local Message-ID: <502D56E4.2080705@FreeBSD.org> Date: Thu, 16 Aug 2012 21:24:04 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org References: In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8FC7886DD4A652E2CFD96DD1" X-Virus-Scanned: clamav-milter 0.97.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: Subject: Re: Get ports tree of the current pkgng repository X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2012 20:24:17 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8FC7886DD4A652E2CFD96DD1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 16/08/2012 20:56, Michael Schnell wrote: > Hi, > I don't know if this came up already, but not as far as I know. So, I > was thinking it would be nice to add a mechanism to pkgng, which enable= s > the user to get the ports tree corresponding to the current repository.= >=20 > At least I've the problem that I really like the idea of the pkgng > system, but I need a few custom build packages. For instance rawtherape= e > is not working for me with OpenMP, so I have to disable it to get it > working, or I made some patches for openbox, which of course then needs= > to be compiled. In order to get not in conflict with a more recent > ports tree the exact version of the repository build would be nice. >=20 > At the moment I can think of two ways to implement it. The easiest way > would be to add the ports tree as a packages into the repository. A mor= e > complicated thing is to add a mechanism to portsnap synchronised with > the pkgng system to direct fetch it, or at least a revision number of > the current repo, so you can check it out of the subversion. >=20 > How do you guys feel about this? Could you open an issue on github please? [*] https://github.com/pkgng/pkgng/issues?state=3Dopen Adding a package with a complete ports tree is an ... interesting ... idea. Maybe doable --- but it would be a huge package. Adding some metadata to the repo catalogue to show eg. the SVN revision number of the ports tree used to generate the packages would be a pretty reasonable approach. However, one of the development aims for pkgng is to make it much easier for people to maintain their own packages of the particular software that is important to them, but be able to use a regular public repository for pretty much anything else. That implies being able to handle a mix of packages compiled from different ports trees much better than is the case at the moment. If we get that right, keeping ports trees in precise synch as you describe shouldn't be any great issue. Cheers, Matthew [*] A pull request with patches would be even better, but we're glad of any good ideas. --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enig8FC7886DD4A652E2CFD96DD1 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/ iEYEARECAAYFAlAtVusACgkQ8Mjk52CukIzoYACfWXwnsHcVnKVuuOC4KsBPIvk0 QC4An2XnylNWadvzcTHffsevaIDocBPz =RshU -----END PGP SIGNATURE----- --------------enig8FC7886DD4A652E2CFD96DD1--