From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: specifying workbook dir for dist-hook
Date: Wed, 27 Mar 2002 13:17:14 -0800 [thread overview]
Message-ID: <E16qKnC-0007VQ-00@giblet> (raw)
Rob,
since we're moving TODO and BUGS (and maybe in the future other things)
out of guile-core/ into workbook/, it behooves us to figure out how to
get these files back into the tree on release. apparently, automake
supports "dist-hook", which we currently use in these makefiles:
./doc/Makefile.am
./guile-readline/Makefile.am
it is easy to add something like:
dist-hook:
@echo doing dist-hook...
if MAINTAINER_MODE
@echo 'This is a snapshot of the TODO file.' > TODO
@echo >> TODO
cat $(workbook)/tasks/TODO >> TODO
$(workbook)/../scripts/render-bugs $(workbook)/bugs > BUGS
endif
to top-level Makefile.am. the question is how to define $(workbook)?
we can either require maintainers to specify this directory like:
make workbook=some/path/to/workbook dist
or adopt the convention that workbook is always at
$(top_srcdir)/../workbook and codify that in Makefile.am.
so: what is your preference?
what other files can we factor out of guile-core/?
where would we put them in workbook/?
where is a good place to document all this? (RELEASE?)
if you see where i'm going w/ this, you can obviously make the changes
yourself, but i'm happy to do them for you if given reasonable answers.
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-03-27 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 21:17 Thien-Thi Nguyen [this message]
2002-03-31 1:27 ` specifying workbook dir for dist-hook Thien-Thi Nguyen
2002-04-01 0:09 ` Marius Vollmer
2002-04-01 2:05 ` Rob Browning
2002-04-01 8:53 ` Thien-Thi Nguyen
2002-04-01 18:47 ` Neil Jerram
2002-04-01 19:41 ` Thien-Thi Nguyen
2002-04-01 22:08 ` Neil Jerram
2002-04-03 18:43 ` Marius Vollmer
2002-04-03 20:06 ` Thien-Thi Nguyen
2002-04-07 13:04 ` Marius Vollmer
2002-04-07 22:55 ` Thien-Thi Nguyen
2002-04-08 0:06 ` Marius Vollmer
2002-04-08 2:50 ` Thien-Thi Nguyen
2002-04-08 16:28 ` Marius Vollmer
2002-04-08 19:26 ` Thien-Thi Nguyen
2002-04-08 23:56 ` Thien-Thi Nguyen
2002-04-09 16:58 ` Marius Vollmer
2002-04-09 17:09 ` Marius Vollmer
2002-04-01 20:07 ` 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=E16qKnC-0007VQ-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).