From owner-freebsd-stable@FreeBSD.ORG  Thu Aug 16 20:02:35 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 60C57106566C;
	Thu, 16 Aug 2012 20:02:35 +0000 (UTC) (envelope-from s-tlk@s-tlk.org)
Received: from mail.s-tlk.org (s-tlk.org [178.63.70.119])
	by mx1.freebsd.org (Postfix) with ESMTP id 20ACF8FC0A;
	Thu, 16 Aug 2012 20:02:34 +0000 (UTC)
Received: from [10.0.3.6] (unknown [10.0.3.6])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.s-tlk.org (Postfix) with ESMTPSA id 0EFE3AE0F74;
	Thu, 16 Aug 2012 21:56:01 +0200 (CEST)
Date: Thu, 16 Aug 2012 21:56:00 +0200 (CEST)
From: Michael Schnell <s-tlk@s-tlk.org>
X-X-Sender: michi@priv.s-tlk.org
To: freebsd-stable@freebsd.org
Message-ID: <alpine.BSF.2.00.1208162138370.7693@priv.s-tlk.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: freebsd-ports@freebsd.org
Subject: 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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 20:02:35 -0000

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 enables
the user to get the ports tree corresponding to the current repository.

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 rawtherapee
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.

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 more
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.

How do you guys feel about this?


Greetings
Michael