public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Anthony Green <green@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: RPM notes
Date: Mon, 04 Mar 2002 13:00:00 -0000	[thread overview]
Message-ID: <87zo1odnu9.fsf@creche.redhat.com> (raw)
In-Reply-To: Anthony Green's message of "03 Mar 2002 00:20:10 -0800"

>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:

Anthony> * We currently create two kinds of RPMs..
Anthony> rhug-PACKAGE-VERSION and rhug-PACKAGE-VERSION-devel.

I think it would make sense to generate all the RPMs for a given
package at once: the ordinary bytecode RPM, plus the corresponding
devel package, plus both rhug packages.  This might mean coordinating
with the vendors in some way.  What do you think of that?  The benefit
is version consistency, and also single ownership of the .jar file.

Anthony> * Normally non-devel library RPMs contain *.so.* , and not
Anthony> *.so files (which go in -devel).  However, our classloader
Anthony> currently looks for *.so files, so we must include those in
Anthony> the non-devel package.  Should we change the classloader?
Anthony> How would it know which version to load?

Actually the problem is lower than the classloader; we use libltdl to
load the libraries.  Whatever it decides is what happens.

This is great work, btw.

Tom

  reply	other threads:[~2002-03-04 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-03  0:19 Anthony Green
2002-03-04 13:00 ` Tom Tromey [this message]
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=87zo1odnu9.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=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).