Date: Sun, 12 May 1996 10:23:08 +0200 (MET DST) From: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de> To: ANDRSN@HOOVER.STANFORD.EDU (Annelise Anderson) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-questions@FreeBSD.org Subject: Re: Upgrading 2.0.5 to 2.2-SNAP Message-ID: <199605120823.KAA26318@gilberto.physik.rwth-aachen.de> In-Reply-To: <01I4KTXZV7J6005GN8@HOOVER.STANFORD.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
[...]
> I looked at the 2.2-SNAP files in the src directory on ftp.freebsd.com,
> and they are organized in an entirely differently way from the "current"
> and "stable" sources, as would be expected since they are not a sup
> target. I don't know exactly what to get and how to arrange it so that
> I can do the build. I've looked at the handbook and it doesn't seem to
> be there, but if it is I will be happy to read it.
This is because a SNAP is a made like a RELEASE while -stable and
-current are checked out trees.
Do the following:
get the 2.2-960501-SNAP/src contents onto your machine.
Then you need to build some script that unpacks the sources.
I'm doing it most of the time by doing an ls >file
vi: %s/^s// and %s/\.*$// and then pipe that file through sort and uniq.
^strips the leading s and the trailing .aa suffixes.
You then have a list of names which you can feed so something like
(bourne shell): (assume your files are in /usr/tmp)
cd /
for i in `cat file`
do
cat /usr/tmp/s$i* | tar zxvf -
done
There were times when there was an extract.sh in that directory which did
the above (sure more elegantly) and the code for this can surely
be found in the install scripts in /usr/src/etc/...
>
> Annelise
>
> ::--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
>
>
--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605120823.KAA26318>