* 1.5 doc/Makefile.am uses ../scripts, but ../scripts is only in HEAD.
@ 2002-07-20 20:45 Rob Browning
2002-07-20 21:06 ` Rob Browning
0 siblings, 1 reply; 3+ messages in thread
From: Rob Browning @ 2002-07-20 20:45 UTC (permalink / raw)
I guess I'll presume that ./scripts is supposed to be in 1.5 as well
and copy it over. Let me know whether or not that's OK. I'll hold
off the release until I hear back.
(Aside: looks like alpha.gnu.org is down. Hmm...)
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 1.5 doc/Makefile.am uses ../scripts, but ../scripts is only in HEAD.
2002-07-20 20:45 1.5 doc/Makefile.am uses ../scripts, but ../scripts is only in HEAD Rob Browning
@ 2002-07-20 21:06 ` Rob Browning
2002-07-23 22:05 ` Marius Vollmer
0 siblings, 1 reply; 3+ messages in thread
From: Rob Browning @ 2002-07-20 21:06 UTC (permalink / raw)
Rob Browning <rlb@defaultvalue.org> writes:
> I guess I'll presume that ./scripts is supposed to be in 1.5 as well
> and copy it over. Let me know whether or not that's OK. I'll hold
> off the release until I hear back.
Oops. Ignore that.
I apparently need to rearrange my local cvs checkouts. I keep a full
cvs tree in devel/guile/cvs/ (so I'll see all the new modules when I
update it), and I also keep devel/guile/core-1.4 and
devel/guile/core-1.5 for working on the branches. So I have these
trees to work on:
devel/guile/cvs/guile-scripts
devel/guile/cvs/workbook
...
devel/guile/cvs/guile-core - for HEAD
devel/guile/core-1.4
devel/guile/core-1.5
but at the moment, we hard-code ../FOO for workbook, scripts, etc., so
I can't autogen.sh or "make dist" successfully from core-1.4 or
core-1.5. Though I suppose we could add --workbook and --scripts args
to autogen.sh, I'm also happy to just rearrange my setup to whatever's
the "preferred" approach. I'm guessing that would be more like this:
devel/guile/core-1.4
devel/guile/core-1.5
devel/guile/core -> cvs/guile-core
devel/guile/scripts -> cvs/guile-scripts
devel/guile/workbook -> cvs/guile-workbook
I want to keep the full cvs checkout together because then one command
updates all the modules in there at once.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 1.5 doc/Makefile.am uses ../scripts, but ../scripts is only in HEAD.
2002-07-20 21:06 ` Rob Browning
@ 2002-07-23 22:05 ` Marius Vollmer
0 siblings, 0 replies; 3+ messages in thread
From: Marius Vollmer @ 2002-07-23 22:05 UTC (permalink / raw)
Cc: guile-devel
Rob Browning <rlb@defaultvalue.org> writes:
> Though I suppose we could add --workbook and --scripts args to
> autogen.sh,
Don't we have that already?
#!/bin/sh
# Usage: sh -x ./autogen.sh [WORKBOOK]
But I just noticed that am/maintainer-dirs does not make use of this.
We could let autogen.sh generate some file with the workbook location
in it and use that during configure.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-07-23 22:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-20 20:45 1.5 doc/Makefile.am uses ../scripts, but ../scripts is only in HEAD Rob Browning
2002-07-20 21:06 ` Rob Browning
2002-07-23 22:05 ` Marius Vollmer
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).