Date: Thu, 13 Sep 2012 12:59:04 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Markiyan Kushnir <markiyan.kushnir@gmail.com> Cc: freebsd-arch@freebsd.org Subject: Re: Removing CVS from HEAD Message-ID: <86ehm65guf.fsf@ds4.des.no> In-Reply-To: <505187E4.6060404@gmail.com> (Markiyan Kushnir's message of "Thu, 13 Sep 2012 10:14:44 %2B0300") References: <CAF6rxgnZGjzm230sZXVXxmE7wPowF_BZqbwRjdvz8oV-03gS=A@mail.gmail.com> <505187E4.6060404@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Markiyan Kushnir <markiyan.kushnir@gmail.com> writes: > As a desktop user, I'm OK with the idea. However I have a concern on > using csup after Feb 2013. In my "custom upgrade" scenario (I use it > on my desktops, almost fully automated), I start with, roughly: > > % pkg_delete -adf > % [some extra cleanup] > % csup <supfile-for-a-new-release> > % [build and install the base system] > % [build and install my batch of ports] > > After pkg_delete I have a clean base system "old" release, and at this > point I'm able to update the base source tree before I proceed with > the building of the new world/kernel. After Feb, 2013 I wouldn't be > able to do it. [...] Do you have suggestions how I could adjust my > scenario to update /usr/src the new way? If I understand correctly, this is the procedure you use to upgrade from one release to another? I would recommend sticking with binary releases and using freebsd-update(8) to update and upgrade. If you really want a source tree, however, you can get one using svn. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ehm65guf.fsf>