From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: autogen.sh now requires workbook specification
Date: Sun, 31 Mar 2002 23:00:22 -0600 [thread overview]
Message-ID: <87pu1kdndl.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E16rokn-0007Oc-00@giblet> (Thien-Thi Nguyen's message of "Sun, 31 Mar 2002 15:28:53 -0800")
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
next prev parent reply other threads:[~2002-04-01 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 23:28 autogen.sh now requires workbook specification Thien-Thi Nguyen
2002-04-01 5:00 ` Rob Browning [this message]
2002-04-01 5:17 ` Rob Browning
2002-04-01 19:29 ` Thien-Thi Nguyen
2002-04-01 7:37 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pu1kdndl.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).