Date: Fri, 17 Oct 2003 01:47:58 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Antoine Jacoutot <ajacoutot@lphp.org> Cc: freebsd-questions@freebsd.org Subject: Re: ports security updates branch Message-ID: <20031017084758.GB3259@rot13.obsecurity.org> In-Reply-To: <3F8F9E9C.1070909@lphp.org> References: <3F8F9E9C.1070909@lphp.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--hQiwHBbRI9kgIhsi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 17, 2003 at 09:47:40AM +0200, Antoine Jacoutot wrote: > Hi :) >=20 > This might be a dumb question, but I was wondering if a king of "stable= =20 > branch" existed for the ports tree. Under OpenBSD I think you can follow= =20 > the ports tree stable branch so you only get security updates for your=20 > ports. > This does not seem possible under FreeBSD, if I understood correctly=20 > only the current branch (tag=3D.) is used for ports; at least this is wha= t=20 > I always used... > Now, here are my questions about that: > - is there a way to only get the security updates for ports ? (are=20 > security updates for ports included in the FreeBSD security advisories) > - when upgrading to a new release, can I use the release branch for ports= ? >=20 > The reason I'm asking this is that I don't want to update my ports=20 > everytime a new version comes out... except if it has a security issue. FreeBSD doesn't provide this. Since our ports collection is about 5 times the size of OpenBSD's it's too much work. Kris --hQiwHBbRI9kgIhsi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/j6y+Wry0BWjoQKURAvnaAJ4tVqYFDIhFsJc/QMsZSFhUuQyzZwCfWl3/ 7mM3INWB9I4OXz4Hd0ABb1w= =xlmF -----END PGP SIGNATURE----- --hQiwHBbRI9kgIhsi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031017084758.GB3259>