From nobody Sun Nov 14 17:23: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 A8CA51839EF8 for ; Sun, 14 Nov 2021 17:23: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 4HsfL520rbz3k3x for ; Sun, 14 Nov 2021 17:23:25 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1mmJDu-0008Gc-Uh; Sun, 14 Nov 2021 18:23:22 +0100 Date: Sun, 14 Nov 2021 18:23:22 +0100 From: Kurt Jaeger To: Guido Falsi Cc: freebsd-ports@freebsd.org Subject: Re: Adding functionality to a port Message-ID: References: <4ca51765-b556-3f12-5809-5aadbf6dccca@ohreally.nl> <480b44f5-0674-e645-8413-a1a368cfc393@ohreally.nl> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: 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: X-Rspamd-Queue-Id: 4HsfL520rbz3k3x X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-ThisMailContainsUnwantedMimeParts: N 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 ?