Date: Sun, 14 Nov 2021 22:39:39 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: Rob LA LAU <freebsd@ohreally.nl>, ronald-lists@klop.ws, freebsd-ports@freebsd.org Subject: Re: Adding functionality to a port Message-ID: <1b4e941d-841a-fa14-799e-d0655d5a82ec@quip.cz> In-Reply-To: <0730c6f7-ca23-d40f-c395-d20bc1be6816@ohreally.nl> References: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl> <op.1cuttdn3kndu52@joepie> <0730c6f7-ca23-d40f-c395-d20bc1be6816@ohreally.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14/11/2021 16:56, Rob LA LAU wrote: > Thanks Ronald. But I'm not asking how or where to report bugs. > > Allow me to rephrase my question. > > If and when I am a FreeBSD port maintainer, can I just add any scripts > or other files to the port I maintain if I think they may be practical, > even if those files are not part of the upstream project? If you want simple answer, then YES. Almost all SW in ports are developed without FreeBSD in mind and does not contain FreeBSD compatible rc script to start the service so the maintainer needs to write some. And periodic scripts are again very FreeBSD specific, not included in the upstream. Both (rc and periodic) scripts are in maintainer's hands. Some ports without these additional scripts will be almost useless. But if you are asking if maintainer can add any malicious code then the answer is NO and port committers are doing their best to not commit it. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1b4e941d-841a-fa14-799e-d0655d5a82ec>