Date: Tue, 18 Oct 2016 14:52:34 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: Mark Linimon <linimon@lonesome.com> Cc: freebsd-ports@freebsd.org Subject: Re: private ports and pkgs versioning Message-ID: <ea8b000b-11a3-1b9d-e877-004e3873d782@freebsd.org> In-Reply-To: <20161018125414.GA18517@lonesome.com> References: <1cba6ef9-89af-c3b8-48df-0cbdc8499b6c@freebsd.org> <ed1e5d26-3a0f-3889-665f-5e32dc708c7f@FreeBSD.org> <20161018125414.GA18517@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --c3mG4b8Vqs55urubdw8LqKbN8qTgxAVhj Content-Type: multipart/mixed; boundary="6WUJBtrV9EED5DE67qffHCWqwIqNmTke6"; protected-headers="v1" From: Matthew Seaman <matthew@freebsd.org> To: Mark Linimon <linimon@lonesome.com> Cc: freebsd-ports@freebsd.org Message-ID: <ea8b000b-11a3-1b9d-e877-004e3873d782@freebsd.org> Subject: Re: private ports and pkgs versioning References: <1cba6ef9-89af-c3b8-48df-0cbdc8499b6c@freebsd.org> <ed1e5d26-3a0f-3889-665f-5e32dc708c7f@FreeBSD.org> <20161018125414.GA18517@lonesome.com> In-Reply-To: <20161018125414.GA18517@lonesome.com> --6WUJBtrV9EED5DE67qffHCWqwIqNmTke6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/18/16 13:54, Mark Linimon wrote: > On Tue, Oct 18, 2016 at 08:49:06AM +0100, Matthew Seaman wrote: >> Yes, there is a lot of useful stuff in the ports tree to support local= >> ports or even whole local categories of ports. I can't recall now how= I >> learned about all this stuff -- it may well have been just be a >> combination of reading Makefiles and hints dropped on mailing lists. = I >> cannot recall a document describing this stuff anywhere. >=20 > I don't believe that there is one. >=20 > I'm sure there are N locally-grown solutions out in the wild. >=20 > We ought to work together to poll people on what they use. >=20 > As for adding the category, I think there's a quick fix, if you don't > care about building INDEX. Add USE_LOCAL_MK=3Dyes to your Makefile > invocations, and use the patch below. >=20 > Note: I haven't tried this yet, so adding the category to ports/Makefil= e > may also be necessary to pacify ports/Mk/bsd.port.subdir.mk (e.g. INDEX= =2E) >=20 > Index: ports/Mk/bsd.local.mk > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- ports/Mk/bsd.local.mk (revision 423944) > +++ ports/Mk/bsd.local.mk (working copy) > @@ -14,6 +14,8 @@ > # time should live. > # > =20 > +VALID_CATEGORIES+=3D local > + > .endif # !defined(_POSTMKINCLUDED) && !defined(Local_Pre_Include) > =20 > .if defined(_POSTMKINCLUDED) && !defined(Local_Post_Include) >=20 > mcl >=20 In many places in the ports you can drop in a Makefile.local that gets unconditionally included into the existing Makefile at that level. There are several names that get treated similarly -- so you can have (I think) Makefile.amd64 which is only included when compiling for that architecture. The idea being if you add a whole new file, you won't get merge conflicts when updating from SVN. There's a Makefile.inc that goes one level above that gets included similarly. Unfortunately it looks like this doesn't apply at the very top level of the ports, otherwise this would be a really easy way of adding a custom category. Hmmm... looks like this is handled in the 30 or so lines starting at line 1179 of bsd.port.mk Cheers, Matthew --6WUJBtrV9EED5DE67qffHCWqwIqNmTke6-- --c3mG4b8Vqs55urubdw8LqKbN8qTgxAVhj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYBikiAAoJEABRPxDgqeTn8qMQALGseBCozFHSDqA81uiae7/Y 7d9Er+AH/I7LRNBv8FqNs960TGyYyLKG5QXZ0lLxliZv/+jrV+BTtZQ7Z04wiaiH kQIYcuVaPF+BLsxDv2MrKJYLlibCbx3sRGzlDncRqTOaTsyeK//2TYO1s0OUNI3T ek6sO76t0T+WYt2OKsHEgURmytE/XewT62299eYBOvIRsxJFF3DVQ7h0Bg8AkAyL Xcb6iJwwpebLyOnT20yGmaFBdGi5CUbhmsweVOZEq0fTunrF+6dZ4lUna2fTBkzP 4Nts+qOAY0I2FnvjOqJZf0KFVt1l3RW4d1uhoUcUWelGrUehtYP5n4MGAtzcpi89 VhPogI0kQYE1xhZj4YPvXDpYzecPO8xbQh2MpZFhjVR9BByq9IXx1degINFaleUE WVw7tHVeUIu1GmREO8c3035ESCTca2wqB7dMbJxJuDhYkQHkNvc0arwX5vdHKcEC lhFe6bDwXnA1uDmOGMYoyJNG22NgP3MkSXQySX4a4ORP1/pU3L+wmSm5B/f89Mv7 az0z5AKbNAWD2rfrI6HYz80k3voNlSvWAufG9MpGXcDxYnGPE2psiFuHIkLEzl/+ pI/QMLf2JQOiZLgOTHytAQELLP8QQreBqayt3M7VBPGreymafBZUx/cFO8SAt9U4 l4LqalpNb7gwzNgPBist =hLNx -----END PGP SIGNATURE----- --c3mG4b8Vqs55urubdw8LqKbN8qTgxAVhj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea8b000b-11a3-1b9d-e877-004e3873d782>