From nobody Sun Nov 14 21:39:39 2021
X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F3A45185B2D5
	for <freebsd-ports@mlmmj.nyi.freebsd.org>; Sun, 14 Nov 2021 21:39:49 +0000 (UTC)
	(envelope-from SRS0=Yejt=QB=quip.cz=000.fbsd@elsa.codelab.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4Hsm1x5gv4z4mFm
	for <freebsd-ports@freebsd.org>; Sun, 14 Nov 2021 21:39:49 +0000 (UTC)
	(envelope-from SRS0=Yejt=QB=quip.cz=000.fbsd@elsa.codelab.cz)
Received: from elsa.codelab.cz (localhost [127.0.0.1])
	by elsa.codelab.cz (Postfix) with ESMTP id D500F28417;
	Sun, 14 Nov 2021 22:39:41 +0100 (CET)
Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by elsa.codelab.cz (Postfix) with ESMTPSA id 8EAA128411;
	Sun, 14 Nov 2021 22:39:40 +0100 (CET)
Subject: Re: Adding functionality to a port
To: Rob LA LAU <freebsd@ohreally.nl>, ronald-lists@klop.ws,
 freebsd-ports@freebsd.org
References: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl>
 <op.1cuttdn3kndu52@joepie> <0730c6f7-ca23-d40f-c395-d20bc1be6816@ohreally.nl>
From: Miroslav Lachman <000.fbsd@quip.cz>
Message-ID: <1b4e941d-841a-fa14-799e-d0655d5a82ec@quip.cz>
Date: Sun, 14 Nov 2021 22:39:39 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-ports
List-Help: <mailto:ports+help@freebsd.org>
List-Post: <mailto:ports@freebsd.org>
List-Subscribe: <mailto:ports+subscribe@freebsd.org>
List-Unsubscribe: <mailto:ports+unsubscribe@freebsd.org>
Sender: owner-freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
MIME-Version: 1.0
In-Reply-To: <0730c6f7-ca23-d40f-c395-d20bc1be6816@ohreally.nl>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4Hsm1x5gv4z4mFm
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-ThisMailContainsUnwantedMimeParts: N

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