Date: Mon, 22 Aug 2005 14:22:43 -0700 From: Colin Percival <cperciva@freebsd.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf newvers.sh Message-ID: <430A4223.6080009@freebsd.org> In-Reply-To: <200508221615.37569.jhb@FreeBSD.org> References: <200508190356.j7J3uj5D095435@repoman.freebsd.org> <200508221357.05742.jhb@FreeBSD.org> <430A24F3.3080505@freebsd.org> <200508221615.37569.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Monday 22 August 2005 03:18 pm, Colin Percival wrote: >>I don't require that people install a fixed set of distributions. In older >>releases people can specify which "branch" of the release they want >>(crypto, nocrypto, krb4, krb5) because there are multiple versions of some >>files, but in recent releases there's only one version of each file, and >>FreeBSD Update just updates whatever it finds. > > So how does it know when to add a new file? For example, if I didn't install > the man dist and a new program is added, will it include both the new program > and the manpage or just the new program? FreeBSD Update doesn't know how to add new files; fortunately, it doesn't need to. Security patches don't add new files (or remove them). The problem of upgrading between versions is outside of the scope of FreeBSD Update; it exists _only_ for the purpose of of tracking the RELENG_x_y branches. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430A4223.6080009>