From owner-freebsd-ports@freebsd.org Fri Dec 16 14:17:06 2016 Return-Path: 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 C9C4CC821F3 for ; Fri, 16 Dec 2016 14:17:06 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (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 94EF8EFC; Fri, 16 Dec 2016 14:17:06 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 7103C1AAF014; Fri, 16 Dec 2016 15:17:04 +0100 (CET) Subject: Re: what is the purpose of the quarterly ports branches? To: Willem Jan Withagen , Julian Elischer , freebsd-ports@freebsd.org References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> <1481875278.2027307.820920449.18442D1C@webmail.messagingengine.com> <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> From: Torsten Zuehlsdorff Message-ID: Date: Fri, 16 Dec 2016 15:17:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 14:17:06 -0000 On 16.12.2016 11:38, Willem Jan Withagen wrote: > On 16-12-2016 11:10, Julian Elischer wrote: >> On 16/12/2016 4:01 PM, Dave Cottlehuber wrote: >>> >>> On Tue, 13 Dec 2016, at 23:14, Grzegorz Junka wrote: >>>> I heard that ports' SVN is mirrored to Github. Isn't it enough to just >>>> create a branch or tag for each quarterly release? Even if quarterly >>>> packages are deleted, re-building packages from such branch/tag should >>>> allow to recreate those packages as required since the same code would >>>> give the same packages? >>> These branches already exist BTW: >>> >>> https://github.com/freebsd/freebsd-ports/tree/branches/2016Q3 >> >> the trouble is that the packages are deleted as soon as they are stable. > > It is sort of amusing/depressing/hilarious of all the flavours and ways > everybody works with ports. And I've used them all, just hard core > building, postmaster, portsnap, pouderiere... > Each has its merit, but IMHO everything is not as bad as frozen in stone > CentOS packages. Or Ubunut or or or... One of the big advantages of the portstree is, that you actually get new versions of the software and not just security-fixes. I regularly stumble across actual bugs, which are there for years, just because the are not fixed by purpose. This is really really frustrating. Bringing new versions is a big plus for the ports-tree. And if you don't need them you are free to stay with the old ones. And its easy enough to build and change everything like you want. Ever really tried this for various linux-distros? Its very painful. Greetings, Torsten