Date: Fri, 23 Jun 2017 11:35:01 +0200 From: demelier.david@gmail.com To: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <1498210501.2506.6.camel@gmail.com> In-Reply-To: <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> References: <CAO%2BPfDeFz1JeSwU3f21Waz3nT2LTSDAvD%2B8MSPRCzgM_0pKGnA@mail.gmail.com> <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> <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2017-06-23 at 10:38 +0200, Vlad K. wrote: > But again, that's all doable without having to introduce new > infrastructure. The ports tree as is can be maintained like this and > quarterly repos would NOT be required. All it's needed is for > maintainers to keep a stable version and a latest version. There's > already plenty of ports done like that, otoh postfix and > postfix-current, nginx and nginx-devel, etc... Yes but again if not all ports follow this system, we still have the problem of having potential major upgrades. > Because the BIGGEST problem in maintaining separate "stable" or LTS > branches is BACKPORTING fixes for ports in the #2 category, ie. > those > that mix new features with fixes, so you have to CHERRY PICK only > the > fix and BACKPORT it to your "stable" branch. And that's even more > work > often introducing NEW bugs. Release branches do not need backports. > BTW, the problem of the original post could've been avoided if the > user > only read UPDATING which clearly stated that www/node becomes 7 and > previous node (6) becomes www/node6. (20161207) entry. Completely off topic, if you upgrade the ports tree, you should update all your packages as doing partial upgrades is even worse (shared library rebuilds for instance).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1498210501.2506.6.camel>