Date: Thu, 16 Jul 2015 08:09:39 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: poudriere with custom packages Message-ID: <55A758B3.2050502@FreeBSD.org> In-Reply-To: <55A729C8.10301@ish.com.au> References: <55A729C8.10301@ish.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CgVbGEauVmPcNSDXtIRniO5bWFMhRsOb4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 16/07/2015 04:49, Aristedes Maniatis wrote: > I have a custom built package which I'm building outside the FreeBSD > ports system (using pkg-create commands). How can I add that package > to a poudriere managed repository so that it appears in the package > index and can be easily installed like any other package? >=20 > Thanks for any help I can think of two ways to handle this: 1) Manually build your own repo containing just your custom package. Simply copy the package .txz to a directory accessible from your webserver (or however you want to publish the repo.) Then run 'pkg repo' in that directory. See pkg-repo(8) for the gory details. This fails on your 'poudriere managed' requirement, but it's pretty simple. You could even add your own package to the directory that poudriere creates and then use pkg repo to rebuild the catalogue there. 2) Integrate your custom package into the ports tree. You can add a 'Makefile.local' in /usr/ports containing something like: SUBDIR +=3D myports which adds 'myports' as a new category for your custom stuff. Then just mimic the layout from any of the other categories. This obviously works best if your custom stuff uses the standard ports machinery to build your package. You can then add 'myports/mypackage' to the list of what poudriere should build. I'd be interested to hear about how you are creating packages outside the ports tree. This is something we'd like to facilitate, but at the moment pkg(8) and the ports are deeply entwined and there isn't much useable documentation or prior art for how to do it 'by hand'. Cheers, Matthew --CgVbGEauVmPcNSDXtIRniO5bWFMhRsOb4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iQJ8BAEBCgBmBQJVp1izXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATMiwP/Rjl5AXaOAzsE70l1RQsXINd snmOX9B1FSjWyHajTHMg6vSys7rWPYOJ/qsJwHdEJ6H22sJvWHs8oWunrDVK5t/+ 8bP4yDsyTJJ+XbuY5r+awqcDXufNH4fJPLdckiUE1g/SlGBpv7zhhT6bv4NmAtny Cn8SesBJgEqoyFeuYAGxLmBDpUdUjEkJwx8vGc0vuicYWz4PSsvoUNM7bbXA8KMA kl7MNYngw90w27QqQopcotJa5TWpBssRCMkepSSJn1tNZnGyYybOeZ1InJOJJC/V 1MZ7fE6G5RbGXBXSgZb7/qK/b2Yz3gpOwjImSanzWbBqxL096Leh1EPhoLSM8msd 4QZxVoijjD2kAA61updZLuh6Eeshd3gnQAeU/CQk7u/RbWF94SdpOIcqfR0CuAXI Y5/NkP9j/zug17fjIau4FIHms+Hpz/wnHpoLUxEioo2sq5xKLuWThpU72U355A2V vAIB0/yJHfmx4TSjfSofaEkGDCFUgLAvwD6bD6T+hXUdjLQDg9tKKHHZf6cuktBw 06yMKQJtrXWpPoZBDA2fWeDgZl0gX/cX6zxQ9bva6voxWX34jUd7w+YQyMKiBkbz d4qx96Pfxm6FFghoozn/20Sd0/Sx/V95SexOX1tD2GbWuSj2H+a40C1jqjEW/Brz q8sP0AxnD3loVtPc1BTP =2Fg0 -----END PGP SIGNATURE----- --CgVbGEauVmPcNSDXtIRniO5bWFMhRsOb4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A758B3.2050502>