From nobody Sun Nov 14 15:54:22 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 B467D18535E1
	for <freebsd-ports@mlmmj.nyi.freebsd.org>; Sun, 14 Nov 2021 15:54:25 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4HscMP4nxLz4h4J
	for <freebsd-ports@freebsd.org>; Sun, 14 Nov 2021 15:54:25 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.95 (FreeBSD))
	(envelope-from <pi@freebsd.org>)
	id 1mmHpm-00088l-Ae;
	Sun, 14 Nov 2021 16:54:22 +0100
Date: Sun, 14 Nov 2021 16:54:22 +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: <YZExLlXP3uEjrvyF@fc.opsec.eu>
References: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl>
 <YZEskkPi2+cX9hrZ@home.opsec.eu>
 <480b44f5-0674-e645-8413-a1a368cfc393@ohreally.nl>
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
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <480b44f5-0674-e645-8413-a1a368cfc393@ohreally.nl>
X-Rspamd-Queue-Id: 4HscMP4nxLz4h4J
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-ThisMailContainsUnwantedMimeParts: N

Hi!

> On 14/11/2021 16:34, Kurt Jaeger wrote:
> > 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-)
> 
> Don't worry: I don't want to pressure anyone into doing anything. :)
> 
> But I would like to know how much functionality a port maintainer can add
> to a package before it is considered too much.

There's no rule that limits it.

Upstream can also hunt for functional changes 8-) and integrate
them 8-)

> At some point the port will no longer represent the upstream package, and
> I'd really like to know where this limit is.

There are two aspects:

- If the changes are useful, upstream can integrate them...
- If the changes collide with upstream ideas, who's to judge,
  as long as no license issues are created ?

Maybe it makes it easier to understand if you tell us the port
in question ?

-- 
pi@FreeBSD.org         +49 171 3101372                  Now what ?