From: Mark Galassi <rosalia@galassi.org>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: new release soon
Date: Fri, 20 Dec 2002 19:23:00 -0000 [thread overview]
Message-ID: <87ads03nl3.fsf@galassi.org> (raw)
In-Reply-To: <20020418171018.W11579@redhat.com>
Tim> I am planning on making a new release of docbook-utils soon
Tim> (within the next week or two). I don't plan on changing much
Tim> from what is currently in CVS.
Tim> Please take a look and shout if there is something wrong. To
Tim> get a tarball, use 'make -f Makefile.cvs', './configure', and
Tim> 'make dist'.
What a sec, why do things differently? You should do
./autogen.sh
./configure
make distcheck
# (make sure you do "distcheck")
(note the above steps are even more nicely done building in a separate
directory)
and then, since we use automake/autoconf properly, you can build the
RPMs with
rpm -ta docbook-utils-version.tar.gz
then you're done, and all in a gnulitically correct way.
At one point Eric had mistakenly removed docbook-utils.spec from the
EXTRA_DIST and hence made it impossible to do the "rpm -ta
file.tar.gz", but I think I reintroduced it, or in any case it should
be done.
Finally, as you feel you are close to being ready, can you point me to
the tarballs so I can see if they work on solaris? It's always a good
shakeout to test these things on a different OS.
WARNING: multiple messages have this Message-ID
From: Mark Galassi <rosalia@galassi.org>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: new release soon
Date: Thu, 18 Apr 2002 10:47:00 -0000 [thread overview]
Message-ID: <87ads03nl3.fsf@galassi.org> (raw)
Message-ID: <20020418104700.pG9YpYm2syWhF7U1BH2EUL3R2LwggpvDzBTS8RKRpIM@z> (raw)
In-Reply-To: <20020418171018.W11579@redhat.com>
Tim> I am planning on making a new release of docbook-utils soon
Tim> (within the next week or two). I don't plan on changing much
Tim> from what is currently in CVS.
Tim> Please take a look and shout if there is something wrong. To
Tim> get a tarball, use 'make -f Makefile.cvs', './configure', and
Tim> 'make dist'.
What a sec, why do things differently? You should do
./autogen.sh
./configure
make distcheck
# (make sure you do "distcheck")
(note the above steps are even more nicely done building in a separate
directory)
and then, since we use automake/autoconf properly, you can build the
RPMs with
rpm -ta docbook-utils-version.tar.gz
then you're done, and all in a gnulitically correct way.
At one point Eric had mistakenly removed docbook-utils.spec from the
EXTRA_DIST and hence made it impossible to do the "rpm -ta
file.tar.gz", but I think I reintroduced it, or in any case it should
be done.
Finally, as you feel you are close to being ready, can you point me to
the tarballs so I can see if they work on solaris? It's always a good
shakeout to test these things on a different OS.
next prev parent reply other threads:[~2002-04-18 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Tim Waugh
2002-04-18 9:40 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-04-18 10:39 ` Éric Bischoff
2002-12-20 19:23 ` Tim Waugh
2002-04-18 12:24 ` Tim Waugh
2002-12-20 19:23 ` Mark Galassi [this message]
2002-04-18 10:47 ` Mark Galassi
2002-12-20 19:23 ` Tim Waugh
2002-04-18 12:34 ` Tim Waugh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ads03nl3.fsf@galassi.org \
--to=rosalia@galassi.org \
--cc=docbook-tools-discuss@sources.redhat.com \
/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).