Creating custom ports versions.
crux at eckner.net
Mon Nov 25 07:54:19 UTC 2019
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, 25 Nov 2019, KPECT wrote:
> Hi people.
> Very often I use slightly modified ports just to achieve some additional or
> remove some extra options that the original port provides. I'd like to
> suggest to propose implementing a new ports function that would allow users
> to create a child port (for example in /usr/ports/custom) that has the same
> name as the parent, but which has some differences that the user needs.
> Every time the ports are updated if the version of the parent port is
> changed, this also affects the child ports, so you do not need to track them
> Similar solution for FreeBSD can be found here:https://www.amoradi.org/2019/11/12/maintaining-port-modifications-in-freebs
> I belieive that this is very demanded function.
> Best regards,
I would definitely use that feature. My approach so far was:
put patches into /usr/patches/$repository/$port/
and apply them during `ports -u`, resigning the ports using a private key.
The feature itself is implemented as a patch to ports:
What I like about this approach (and what I would like to see in an
official implementation, too), is, that you do not need to modify anything
in order to keep your packages up-to-date - as long as your patches
still cleanly apply.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the CRUX