Date: Fri, 18 Jul 2014 10:44:33 -0400 From: Rick Miller <vmiller@hostileadmin.com> To: Andrew Berg <aberg010@my.hennepintech.edu> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Managing multiple repos with Portshaker/Poudriere Message-ID: <CAHzLAVGZ%2B%2BK3dKQbOhVeVnyL7fH62Emontg-Td9iTiqv-r-eSA@mail.gmail.com> In-Reply-To: <53C9046A.7070805@my.hennepintech.edu> References: <CAHzLAVGY7PgA-b49qiN2m0djUrJKT4kGTkdeNg0BBFNV6O7L5Q@mail.gmail.com> <53C9046A.7070805@my.hennepintech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 18, 2014 at 7:26 AM, Andrew Berg <aberg010@my.hennepintech.edu> wrote: > On 2014.07.18 06:15, Rick Miller wrote: > > 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. > How do you decide which release to use as a tag when there are several > supported releases of FreeBSD at any given time, all of which are equally > supported by the ports tree at that point in time? I failed to mention that we track the FreeBSD source internally which includes customizations. We have implemented an internal versioning scheme. The tags would be representative of the the internal versioning scheme to associate a particular commit to a particular release, similarly to how the FreeBSD project does with subversion[1]. [1] http://svnweb.freebsd.org/ports/tags/ -- Take care Rick Miller
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVGZ%2B%2BK3dKQbOhVeVnyL7fH62Emontg-Td9iTiqv-r-eSA>