autogen.sh now requires workbook specification

autogen.sh now requires workbook specification

[Thien-Thi Nguyen]

basically, if you do "cvs co hack" this is handled w/o changing
autogen.sh invocation.  if you keep workbook in another place,
you need to invoke like:

	autogen.sh /path/to/workbook

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: autogen.sh now requires workbook specification

[Rob Browning]

Thien-Thi Nguyen <ttn@giblet.glug.org> writes:

> basically, if you do "cvs co hack" this is handled w/o changing
> autogen.sh invocation.  if you keep workbook in another place,
> you need to invoke like:
>
> 	autogen.sh /path/to/workbook

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?

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

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

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: autogen.sh now requires workbook specification

[Rob Browning]

Oops, sorry, I missed your earlier mail where you recommended:

> Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
>
>  cvs co hack
>  cd hack
>  for branch in 1-4 1-6 ; do
>      cvs co -d core-$branch -r branch_release-$branch core
>  done

I had actually thought about that, but didn't know that cvs would be
OK with directories not in the module you checked out inside the
module tree...

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: autogen.sh now requires workbook specification

[Thien-Thi Nguyen]

   From: Rob Browning <rlb@defaultvalue.org>
   Date: Sun, 31 Mar 2002 23:17:10 -0600

   I had actually thought about that, but didn't know that cvs would be
   OK with directories not in the module you checked out inside the
   module tree...

i avoid this question by not doing "cvs update" in hack/, but wonder how
cvs would handle that.

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: autogen.sh now requires workbook specification

[Thien-Thi Nguyen]

   From: Rob Browning <rlb@defaultvalue.org>
   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

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel