Date: Mon, 25 Jan 2021 15:10:51 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Guido Falsi <mad@madpilot.net> Cc: "Russell L. Carter" <rcarter@pinyon.org>, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: poudriere merging multiple ports trees Message-ID: <20210125141051.qheedhp76d2ha6zy@ivaldir.net> In-Reply-To: <4990d009-1962-62c2-3f4e-4f62fd03e26d@madpilot.net> References: <3ea16730-84a1-52ce-2251-bdd808fe5c52@pinyon.org> <4990d009-1962-62c2-3f4e-4f62fd03e26d@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--ask4fldvkfqvoyav Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via freebsd-ports wro= te: > On 24/01/21 20:35, Russell L. Carter wrote: > > Greetings, > > I am completely ignorant here and am looking for up to > > date advice on how to get poudriere to build and make > > available package sets from multiple ports trees.=A0 I > > see there is a port "portshaker" that seems to do much > > of what I want. > >=20 > > I can think of possible alternatives: > >=20 > > I can reasonably expect to have my local ports not > > conflict with already existing ports (could be a common > > prefix in the name).=A0 Since I'm using git, I should be > > able to maintain my own branch which layers my own ports > > over upstream and git pull, merge from upstream. > >=20 > > or > >=20 > > I can duplicate the structure and metadata of the existing > > ports tree and add my own ports and leaves in the tree. > > Still have to maintain unique names.=A0 This seems to be > > what portshaker does?=A0 I am guessing that gets me a > > single package repo. > >=20 > > or > >=20 > > Have two ports trees and generate two package repos, but > > then dependencies would be redundantly built, I guess. > >=20 > > What do the professionals do here? >=20 > I've been using portshaker for this (ports-mgmt/portshaker) for this for = a > long time. >=20 > But when the ports tree will be migrated to git in the near future I plan= to > stop using portshakern and use a git repository forked from the main one > (and syncronized to it) with feature branches for any change and some > "build" branches which I checkout in poudriere and to which I merge the > feature branches as needed. >=20 > Git allows for such a workflow and that should also be quite less error > prone. >=20 > BTW I noticed poudriere performs shallow clones for git repos, so it shou= ld > not use up a lot of disk space. Why not using directly overlays, it will simplify everything ;) Best regards, Bapt --ask4fldvkfqvoyav Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAmAO0WgACgkQY4mL3PG3 PlrdMA/9HLOcyFBp32oF93qUTXXi/hcFEYUm6snKqFGXghkQ9+daDFfLI9cM2UJy Wk21JUZ43h5uTqwE6zZ99G5+vXXWX/EkQw8bfYSQFzzftfuVYtHTcP7in9C6uyzn SmgniGHeIuNlC+f/k/PLXdUWcXql6l0eVmE6ljsi1mC/vJw2fflErXMabTSsq1KL YHh/qQpY0MeT2Vd9EHxJMQl+JHNDbiqYylAJmLbLb9v1p5+NMSfYPTtFQHcAxu6P UyROhjD+SY09bjW0iMjhYB4MtbG3OxLIaaiC2f4NzobdTugb9sJQoUEh1aWY4LOd F3z4LoYdz1m5bHTV6z/Wz0XTAjwcr4xZ58I5fIZ4AZ35ZVYh2zJt+V9HfC/vdH9G Dq1Ss6d10F6XNXwOEDM47gS/el2iZGhzNjJ1CsJgMQb4rjYjYpRwev06a6GAMGd9 O779RbinHJuLmzGNbp1dKUvxBQSzz0Aulipl/ew+5Uyj4yF+KDg0FohQ5bSEUsb2 +9VHpUBLtFw4/XcuUU0DdWLE/9AqYcEbst0IhTV45O+731lg+X3UQpniF5inwYYJ StkCNsIM4OrVeAfhVKj/+gomDZ/4Y0VOaWqOH1B4AJuoEGkQfdFywq2GL6Zuthtx F+twDPvePeeIFqIX7uhAhXvA1nDtWxmUqjlsjx85pqjlh38TrEw= =CfIR -----END PGP SIGNATURE----- --ask4fldvkfqvoyav--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210125141051.qheedhp76d2ha6zy>