On 11/7/2014 1:37 PM, Jungle Boogie wrote: > Dear Ingo, Misc > -------------------------------------------- > From: Ingo Schwarze <[email protected]> > Sent: Fri, 7 Nov 2014 19:18:08 +0100 > To: Jungle Boogie Cc: [email protected] > Subject: Re: Updating ports from CVS question > > >> Jungle Boogie wrote on Fri, Nov 07, 2014 at 08:20:36AM -0800: >> >>> Great idea! How do you update your ports, then? >>> Just download a new ports.tar.gz file >> >> If you are running -stable, that doesn't help. >> The file ports.tar.gz doesn't get updated for -stable after release. >> >>> or: >>> # cd /usr/ports >>> # cvs -d [email protected]:/cvs -q up -rOPENBSD_`uname >>> -r | sed 's/\./_/'` -Pd >> >> Yes, you start from ports.tar.gz, and then, you update that tree >> with cvs(1) as needed. >> >> I don't like your uname(1) hackery, though. It's unsafe, giving you >> a false sense of security. For example, i'm running -current, but >> your uname(1) says, on my -current machine: >> >> $ uname -r | sed 's/\./_/' >> 5_6 >> $ uname -a >> OpenBSD isnote.usta.de 5.6 GENERIC.MP#5 i386 > > I followed directions here: > http://www.bsdnow.tv/tutorials/stable-current-obsd > > I did skip one reboot, though. > > Also, I went from 5.6 -release to -current and now looking at the > directions, following a snapshot is recommended. I would expect my > uname to update, though. > > >> >> To update my ports tree, i have to do: >> >> $ cd /usr/ports && cvs -d ... up -dP >> >> without any -r argument, but your uname(1) would give me a bogus -r >> argument, so in some situations, it does the wrong thing. >> >> I'd recommend that you just supply the correct -r by hand if needed. > > I think I'll rebuild the machine based on a snapshot THEN update to > -current! > >> >> KISS! >> >> Yours, >> Ingo >> > > > Hi,
It has been stated multiple times on this list that snapshots do not necessarily equate to -current. I think it's generally in reference to the base system and not ports, but it is something to be aware of. From: http://www.openbsd.org/faq/faq5.html "Third, snapshots often contain experimental code that isn't yet committed to the tree." It has been my experience that if you want to follow snapshots, then it is best to download the ports.tar.gz at the time that you install the snapshot. This has the greatest chance of success (though not guaranteed), as the cvs and the snapshot can be out of date. For example, a snapshot may be complied on Monday, you download it on Thursday, and in the meantime, someone has updated a port in CVS. It's only bitten me a couple of times in the last 10 years, but when it does, it really sucks. What you think should be a 5 minute operation turns into a system upgrade! lol Using ports and snapshots (rather than packages) can be quite resource intensive. For giggles,yesterday I compiled a few ports that I normally use packages for (I wanted to test my VM, as well as see what it took to compile mariadb). To compile, the dependencies for 2 of the packages I usually install pulled (ftp/compile) around 100 packages. I ended up with 5 versions of autoconf 2 versions of automake and TONS of things I would not normally install... Having the ports.tar.gz that corresponds to the snapshot you install is nice because 2 months down the road you can compile/install something that will work on your system even when there is no package available that will work on your system. If you try to cvs up your ports to -current 2 months after installing a snapshot, odds are that something won't compile. OpenBSD works FANTASTIC as long as you keep things consistent. Follow base, -current, or snapshots. Don't try to mix and match and you should have smooth sailing. That's just been my personal experience. Other people way more authoritative may have much wiser advice. Cheers, Steve Williams
