Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Patch 00007
Message-ID: <1992Sep22.035045.12585@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <q597lis@sgi.sgi.com>
Date: Tue, 22 Sep 92 03:50:45 GMT
Lines: 63
In article <q597lis@sgi.sgi.com> rpw3@rigden.wpd.sgi.com (Rob Warnock) writes:
>terry@cs.weber.edu (A Wizard of Earth C) writes:
>+---------------
>| In a standard (default) installatiom, /sys is a symbolic link to
>| /usr/src/sys.386bsd and /usr/include/sys is a symbolic link to /sys/sys.
>+---------------
>
>The original README for the patch kit said that it would work on relative
>directory paths, but it won't. Nor will it work on relative paths to the
>sources. This is making it *very* hard to maintain multiple development
>trees and still try to track these (semi-)official patches.
I intended this to mean a relative location for the installation
of the patchkit software, nt the software being patched (see the previous
posting, since this bears on the problem).
The "relative paths" to the sources problem is a horse of a
different wheelbase. The problem here is an inability to track multiple
instances of patch installation.
As a temporary workaround (I don't have a permanent one, since
symbolic links are not currently in use for all sources, like they probably
should be -- but then again, we're only on release 0.1 for 386BSD):
1) cd /usr
2) mv src src.primary
3) ln -s src.primary src
One can then change the symbolic link as required to get at different
source trees. Obviously, not using the "/sys" symbolic link was a
mistake (I used absolute real paths to all files). The problem with
doing this, however, is that not all sources have a convenient symbolic
link lying around -- take everything except the kernel code under /usr/src,
for example.
This, in combination with installing the patchkit under /usr/src.primary
and all other seperately maintained trees (requires changing "PATCHDIR"
in each instance of the "PATCHES" program) should provide what you are
looking for.
Short of a CVS like system for patches, I can't think of a real soloution
for multiple source trees that is any simpler.
PS: Anyone who has downloaded the Alpha-3 software: If you got the "README"
file with the tar file (the one that is seperate, *not* the one in /patch!),
rather than the "patchkit-0.1.README", download it again. I had uploaded
the wrong directory contents (see previous posting).
Terry Lambert
terry_lambert@gateway.novell.com
terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------