From: Anthony Green <green@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: rhug build changes
Date: Sat, 02 Mar 2002 15:16:00 -0000 [thread overview]
Message-ID: <1015111002.1926.46.camel@dhcppc2> (raw)
I'm making some changes to how rhug is built today.
One of the problems with the current scheme is that it is difficult to
generate RPMs in an ordinary way. That is, by running "make dist" to
generate a PACKAGE-VERSION.tar.gz file and then using a spec file turn
that into various RPMs.
If you try running "make dist" now, it treats rhug as a single big
package. My plan is to break it down a bit so each sub-project can
really stand alone. I still want to be able to be able to configure and
build the entire tree in one go, but I also want to be able to create
stand-alone .tar.gz and RPM files for each project in rhug.
This can be done incrementally. I'm about to commit configury changes
and a spec file for xerces, and I'll keep going from there. Right now
I'm prefixing the distro and package names with rhug- so there won't be
any confusion with some other xerces tar-ball/RPM files.
I don't have much experience with RPM, so comments on my spec file (and
anything else) are welcome. I think much of the spec file can be
generated from the info.rml files, which are also used to update the web
pages. I'll try that later.
AG
reply other threads:[~2002-03-02 23:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1015111002.1926.46.camel@dhcppc2 \
--to=green@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).