From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: autogen.sh now requires workbook specification
Date: Sun, 31 Mar 2002 23:37:24 -0800 [thread overview]
Message-ID: <E16rwNY-0007pN-00@giblet> (raw)
In-Reply-To: <87pu1kdndl.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Sun, 31 Mar 2002 23:00:22 -0600)
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
prev parent reply other threads:[~2002-04-01 7:37 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
2002-04-01 5:17 ` Rob Browning
2002-04-01 19:29 ` Thien-Thi Nguyen
2002-04-01 7:37 ` Thien-Thi Nguyen [this message]
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=E16rwNY-0007pN-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).