Re: autogen.sh now requires workbook specification

[Thien-Thi Nguyen]

   From: Rob Browning <address@hidden>
   Date: Sun, 31 Mar 2002 23:00:22 -0600

   Hmm, so checking out "hack" gets us a subtree like this:

     hack/core
     hack/scripts
     hack/workbook

   and autogen.sh just looks up one level?

apparently.  the code sez:
workbook=../workbook        # assume "cvs co hack"

   This made me wonder about having multiple trees checked out.  For
   example, I always keep a core-1.5 and a core-dev tree checked out and
   jump back and forth between them.  If scripts and workbook are
   supposed to be guile version independent, then am I right in presuming
   that I should probably just not use the "hack" module and manage my
   tree by "hand". i.e. just have separate checkouts for

     guile/core-1.5
     guile/core-dev
     guile/scripts
     guile/workbook

how can anyone presume to ask another person about their own
presumptions?  see:

 http://mail.gnu.org/pipermail/guile-devel/2002-March/004909.html

for a template to start your customization.  perhaps you'd like to write
a general script and contribute it, or adapt one already written.

   Also, if scripts and workbook are supposed to be "core independent",
   people will need to be careful not to accidentally tag them together.

it all depends on what the tag signifies to the programmer.  in some
cases, tagging things together is the preferred way to manage all trees
related to some concept concurrently.

adding branches, on the other hand, does indeed require care to keep
things localized to the relevant cvs modules; workbook and scripts do
not branch, basically.  (branching is implemented by cvs using special
tags, IIRC, so this can be confusing.)  thanks for bringing this up.
i'll add some introductory text to HACKING and to the web pages.

thi