Date: Thu, 22 Jun 2017 15:38:53 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> In-Reply-To: <dahnkctsm1elbaqlarl8b9euouaplqk2tv@4ax.com> References: <CAO%2BPfDeFz1JeSwU3f21Waz3nT2LTSDAvD%2B8MSPRCzgM_0pKGnA@mail.gmail.com> <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <dahnkctsm1elbaqlarl8b9euouaplqk2tv@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG Content-Type: multipart/mixed; boundary="JLqxmnnXNFb3MpKsn8CJl6j8KlCWJSH1K"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Message-ID: <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version References: <CAO+PfDeFz1JeSwU3f21Waz3nT2LTSDAvD+8MSPRCzgM_0pKGnA@mail.gmail.com> <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <dahnkctsm1elbaqlarl8b9euouaplqk2tv@4ax.com> In-Reply-To: <dahnkctsm1elbaqlarl8b9euouaplqk2tv@4ax.com> --JLqxmnnXNFb3MpKsn8CJl6j8KlCWJSH1K Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/06/22 15:03, scratch65535@att.net wrote: > Why don't the same choices apply here? What am I missing? Two things: 1) It's progress in the development of the FreeBSD base system that drives the release cycle. The general state of the ports does not exert much influence on release frequency -- nor should it. 2) Even if we could scrape up enough people to support however many branches you are proposing, remember they are all volunteers. It's hard enough getting people to maintain the existing quarterly branches as it is, and those are relatively short lived so that most merges from head are pretty trivial. People really aren't going to want to do essentially repetitive merges to branches where everything else is up to X years older than head. Which would make it both tedious and frequently difficult to do. Tedious and difficult generally means "you need to pay someone to do that". Which means you need a commercial setup to generate the money to pay all those wages. Which means you -- the end user -- get to pay for the provision of those specially maintained package sets. Now, if you think you have a viable business case for maintaining essentially a static snapshot-plus-security-fixes of the ports and supplying packages generated from it, by all means go ahead and try offering that as a commercial service. I doubt you'll succeed though -- a number of other people[*] have been down that path, and they usually give up fairly early because the market just won't support it at the mome= nt. Cheers, Matthew [*] These guys most recently: http://www.xinuos.com/menu-products/openserver-10 They're still going, but I haven't heard of much activity from them for the last year or so. --JLqxmnnXNFb3MpKsn8CJl6j8KlCWJSH1K-- --QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZS9aFXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTni+wQAIrW5XF87qHWrrsSdadU3qzi IavK9zThc4ALsOaToyW5iiqD3TcvahlrP/90XSVu0uacuSMIjrj/DQdQ2wD7KwlL DekpnnDbgTlEwqJe44Dh/T3Nx1XwwlTdqVqfiaVFK4zxb3/zLG2rJuVUGY2T2dZU ZrWBzdVhpr6ptDnV49KLIGS80wI7fPSJ+/R9fix3RQ/Vcy/TKHnEcZtli6nvcWIP 4nm/254+Peq4QxfpukbJj/dhcbMVZL8pn7z10dQM5r915LaSbVjVobe+efmEJSM4 YOPENahLV5nzShLfx9x3oH6xunG2vHrl21DBLGoO4AVmu9Zo1IlsRRcnmgSBB1S3 ZHrbAGha2SmPbhwXKlQn3DdMq5EvOQN6qYMV5XR7101/+WF8/VdFkZMQ7/kdZvzi lPedsK+ATgeHypg1N1yDYe+gQvYcVRVOOrXoCUmX24MGKmwJX17/DpMIXiCyE0Dq +xxYWhvVerurhqfhdof/PYOeNxoJjYvYsuKensF/XFJuSw+cF3Ii+NF8D0LrbErG oDFvDMLIzQcsL3DrD7dc1zS3cCtG4AlBYeXLxYOhKf80JvVUn2bZpOleFtrlO9GG KBy95cpVJMTubhmCE94bVzb/Jp4Qng31zCLCjPKAoNJ3ZtBVWk3kzGrQ6Wi6ED3Q MDLXb6bLh+cOHO4WpRQy =l/ZF -----END PGP SIGNATURE----- --QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?775ba90e-a811-4cc8-a729-bdc0dad7774c>