From owner-freebsd-questions@freebsd.org Sun Oct 29 07:17:37 2017 Return-Path: Delivered-To: freebsd-questions@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 AE8A9E5BF71 for ; Sun, 29 Oct 2017 07:17:37 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (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 9B66E6F08D for ; Sun, 29 Oct 2017 07:17:37 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (c-73-240-250-185.hsd1.or.comcast.net [73.240.250.185]) by echo.brtsvcs.net (Postfix) with ESMTPS id 864BC3912D; Sun, 29 Oct 2017 00:17:31 -0700 (PDT) Received: from [IPv6:fe80::7102:4df8:1f13:5c55] (unknown [IPv6:fe80::7102:4df8:1f13:5c55]) by chombo.houseloki.net (Postfix) with ESMTPSA id 2D99212A1; Sun, 29 Oct 2017 00:17:30 -0700 (PDT) Subject: Re: When is a FreeBSD port not a port? To: Frank Leonhardt Cc: "freebsd-questions@FreeBSD.org" References: <59F314E5.4080306@fjl.co.uk> <520fa3b2-8be7-8141-7e8d-9a60c6d1a1ed@FreeBSD.org> From: Mel Pilgrim Message-ID: Date: Sun, 29 Oct 2017 00:17:31 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 07:17:37 -0000 On 10/28/2017 21:16, Shane Ambler wrote: > On 27/10/2017 22:46, Matthew Seaman wrote: >> On 27/10/2017 12:13, Frank Leonhardt wrote: >>> I've written a "few" utilities over the years that I've made available >>> in various places, but it might make sense to put them in >>> ports/sysutils. However, they were written on BSD and are therefore not >>> ports. >>> >>> Should I submit them anyway (if I find time to clean them up, of >>> course)? Or if not, any (polite) suggestions as to where I should put >>> them? I don't use GitHub or SourceForge (too old to change my ways, and >>> I normally work off-line anyway). >>> >>> e.g. http://www.fjl.co.uk/free-stuff >>> >> >> By all means, please do submit your FreeBSD specific code as a "port". >> There's precedent -- various ports for periodic jobs or other >> FreeBSD-ish things. We aren't hung up on the precise meaning of "ports" >> -- it's really a collection of software handily prepared to compile >> easily and (increasingly so over time) be made available as pre-compiled >> binary packages. > > The ports and packages system installs and manages software that is not > provided by the base system. It is really about simplifying the process > of downloading, building and installing available software. > > The name may have originated based on the idea of "porting" software to > run on freebsd but it has grown to be more than that now. You may notice > that a lot of software in the ports tree does not need patches to run on > freebsd, so many ports are not "ported" to freebsd, just installed. Alternately, if you feel this is a tool only you would use, but still want to use the Ports Tree, pkg, poudriere, etc. to manage or deploy the tool, you can locally extend the ports tree.