Date: Sun, 14 Nov 2021 16:34:42 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Rob LA LAU <freebsd@ohreally.nl> Cc: freebsd-ports@freebsd.org Subject: Re: Adding functionality to a port Message-ID: <YZEskkPi2%2BcX9hrZ@home.opsec.eu> In-Reply-To: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl> References: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, > I'm wondering what the rules/guidelines are for adding functionality to a > port, that is not in the upstream package. I can't find anything about > this in the porters' documentation. > > Background: > I'm not a porter myself (planning to be one, but that's irrelevant for my > current question). > I ran into a buggy `periodic' script. And when looking for the port > maintainer to report the bug, I found that this script is not part of the > upstream package, but was added to the port by the port maintainer. > So I'm wondering now whether I should report the bug in the `periodic' > script, or ask the maintainer to remove the script from the port (and > maybe submit it as a separate port). Please submit a problem report via bugs.freebsd.org for the port in question. If you provide a patch for the periodic script upstream, that would probably be fine as well, if they accept it. The maintainer can decide what should happen to the buggy script... > And in more general it would be interesting to know when changes made to > a port are considered too drastic, and when port maintainers should be > asked to join the upstream development team instead of (or in addition > to) maintaining the port. You can ask the maintainer if he wants to join upstream, but if there's no interest, there's no need to pressure one into upstream 8-) -- pi@opsec.eu +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YZEskkPi2%2BcX9hrZ>