Date: Fri, 18 Jul 2014 07:15:26 -0400 From: Rick Miller <vmiller@hostileadmin.com> To: FreeBSD Questions <freebsd-questions@freebsd.org>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Managing multiple repos with Portshaker/Poudriere Message-ID: <CAHzLAVGY7PgA-b49qiN2m0djUrJKT4kGTkdeNg0BBFNV6O7L5Q@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi all, I intend to utilize Poudriere to build binary packages for FreeBSD. The initial design includes a private git repo which tracks FreeBSD Ports (from gthub) in a pristine branch. Changes to this pristine branch are merged into another branch which, in addition to the official ports tree, includes a custom category where private ports are committed. A major advantage here is the ability to tag the repo according to OS releases. While planning the deployment of such a strategy, I happened upon a blog post[1] describing a workflow for managing this utilizing portshaker and poudriere to combine the remote freebsd ports tree with an internal private repo. The method described here is appealing as it removes the need to track freebsd-ports internally, but would I then lose the ability to tag specific commits which would be tied to OS releases? [1] http://funcptr.net/2013/12/11/building-custom-ports-with-poudriere-and-portshaker/ -- Take care Rick Miller
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVGY7PgA-b49qiN2m0djUrJKT4kGTkdeNg0BBFNV6O7L5Q>