From owner-freebsd-ports@freebsd.org  Mon Jun 26 07:43:46 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D0D3DA3B68
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 26 Jun 2017 07:43:46 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 C359C6E200
 for <freebsd-ports@freebsd.org>; Mon, 26 Jun 2017 07:43:45 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1dPOgP-000G41-BF; Mon, 26 Jun 2017 09:43:41 +0200
Date: Mon, 26 Jun 2017 09:43:41 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Dave Hayes <dave@jetcafe.org>
Cc: freebsd-ports@freebsd.org
Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version
Message-ID: <20170626074341.GG29157@home.opsec.eu>
References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net>
 <dahnkctsm1elbaqlarl8b9euouaplqk2tv@4ax.com>
 <20170622141644.yadxdubynuhzygcy@ivaldir.net>
 <cc1c38a4-108c-5f3f-7fa1-400fdcf497f6@freebsd.org>
 <ee6fe33b-aa24-ae5f-f652-f940e15c247a@jetcafe.org>
 <1498157001.2235.1.camel@gmail.com>
 <ffe23575-09a8-9e8c-ab21-772ca5e71aa1@jetcafe.org>
 <1498206372.2506.1.camel@gmail.com>
 <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org>
 <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jun 2017 07:43:46 -0000

Hi!

> Thus, in some cases, people demand or insist because they want something 
> they either cannot accomplish themselves, or cannot accomplish in the 
> limited time they have. As far as I have observed, you can't even -pay- 
> the ports experts to do something you might want.

You can discuss the general idea with the foundation. Then give them
the money they estimate for the feature. They'll easily find folks doing it.
It just won't be cheap.

I guesstimate that you need at least 2 person-years to implement a working
scheme that works within the current framework.

-- 
pi@opsec.eu            +49 171 3101372                         3 years to go !