Date: Sun, 14 Nov 2021 18:23:22 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Guido Falsi <mad@madpilot.net> Cc: freebsd-ports@freebsd.org Subject: Re: Adding functionality to a port Message-ID: <YZFGCoblQOHPnPWe@fc.opsec.eu> In-Reply-To: <fb5e514d-1458-9b49-1882-b64d5386cdfa@madpilot.net> References: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl> <YZEskkPi2%2BcX9hrZ@home.opsec.eu> <480b44f5-0674-e645-8413-a1a368cfc393@ohreally.nl> <YZExLlXP3uEjrvyF@fc.opsec.eu> <fb5e514d-1458-9b49-1882-b64d5386cdfa@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > It is also not correct to "commandeer" a port to force users on design > choices in conflict with the upstream project. Is there a section in the ports maintainers guide or somewhere else that mandates this ? -- pi@FreeBSD.org +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YZFGCoblQOHPnPWe>