From: Anthony Green <green@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: RPM notes
Date: Sun, 03 Mar 2002 00:19:00 -0000 [thread overview]
Message-ID: <1015143611.1759.90.camel@dhcppc2> (raw)
I started making RPMs today, and thought I'd share some random notes for
the record...
* I've created nice RPM configury for 4 of the packages: xerces,
gnu.readline, rhino, and jakarta-oro. They're very easy to create once
you have the pattern down.
* We currently create two kinds of RPMs.. rhug-PACKAGE-VERSION and
rhug-PACKAGE-VERSION-devel.
* The non-devel version currently contains executables, .so files and
.jar files. You could argue that the .jar file should go into the
-devel package, but maybe the right thing is to stick them into noarch
packages and make -devel depend on those.
* Normally non-devel library RPMs contain *.so.* , and not *.so files
(which go in -devel). However, our classloader currently looks for *.so
files, so we must include those in the non-devel package. Should we
change the classloader? How would it know which version to load?
* I'm installing the .jar files in $prefix/share/java (but no links to
an ext directory yet -- let's wait for the tools to catch up).
* The packages know whether or not they're being built in a unified
tree, or separately, and set the classpath and -L options appropriately
at configure time.
* I submitted a patch to rpm-list@redhat.com to add support for GCJFLAGS
in RPM. RPM already sets CFLAGS, CXXFLAGS, and FFLAGS appropriately.
GCJFLAGS is an obvious addition, but it's not critical yet.
* I haven't dealt with docs yet (.html files). Most of them will live
in the -devel packages.
* Much of the specs files should be generated from the info.rml files.
* Creating RPMs is easy. Run "make dist" in the package directory to
create rhug-PACKAGE-VERSION.tar.gz, then run "rpm -ta
rhug-PACKAGE-VERSION.tar.gz". It will extract the spec file from the
tar ball and take care of everything.
* Obviously there are no RPMs yet for the latest gcj libs which are
needed to run these things. You have to force the install like so...
"rpm -hiv --nodeps rhug-gnu_readline-0.6-1.i386.rpm" and just put
libgcj.so and friends in your LD_LIBRARY_PATH.
That's it for now.
AG
next reply other threads:[~2002-03-03 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 0:19 Anthony Green [this message]
2002-03-04 13:00 ` Tom Tromey
2002-03-04 13:25 ` Anthony Green
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=1015143611.1759.90.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).