From: Tom Tromey <tromey@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: rhug-list <rhug-rhats@sources.redhat.com>
Subject: Re: [naoko] Updated ant, and fun with yum
Date: Wed, 12 Nov 2003 17:41:00 -0000 [thread overview]
Message-ID: <87llql1oi7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20031112151000.GJ3419@redhat.com>
>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:
>> 4)If I get all the source rpms, what would be the quickest build
>> procedure for the whole set, ie. does the build work accross the set
>> of src rpms?
Gary> I'm not sure what you mean by either of these...
I think he wants to know what order in which he should build the
SRPMs. I thought there was a rebuild script in redhat-java-rpm-scripts,
but now I can't seem to find it.
Tom
next prev parent reply other threads:[~2003-11-12 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 12:58 Gary Benson
2003-11-12 15:04 ` Ray Auge
2003-11-12 15:10 ` Gary Benson
2003-11-12 17:41 ` Tom Tromey [this message]
2003-11-13 10:10 ` Gary Benson
2003-11-13 21:58 ` Ray Auge
2003-11-13 22:05 ` Paul Nasrat
2003-11-12 20:01 ` Anthony Green
2003-11-13 9:50 ` Gary Benson
2003-11-13 22:24 ` Nicholas Wourms
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=87llql1oi7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gbenson@redhat.com \
--cc=rhug-rhats@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).