[Fwd: Re: [architecture] Re: JPackages and ObjectWeb]

[David Walluck <david@xxxxxxxxxxxxxxxxxx>]

Somehow this original message ended up in the wrong place, but now I 
have more time to add to it anyway.

Current Status

Here is a status of the new rpms that have been packaged for objectweb 
related materials.

Here BR = BuildRequires (the package required this in order to build), R 
= Requires (the package requires this in order to run). I only list 
*new* packages that ahd to be built, not ones already in our repository.

asm             1.4.1           (BR: monolog)
c-jdbc          1.0b15          (BR/R: jgroups)
fractal         2.0             (BR: asm jonathan <= 3.0a7 (not 
packaged) R: asm)
jonathan        3.0a10          (BR/R: oldkilim jonathan monolog)
kilim           2.0.32          (BR: monolog)
monolog         1.7             (BR: fractal monolog)
oldkilim        1.1.3

Right now fractal is a problem because of a dependency on an obsolete 
version of jonathan whose source code I can't find even in CVS.

The only option here is to find this source code or, perferably, to 
update the fractal code. Or, if monolog could be changed to no longer 
require it, I can just remove it from the repository and not worry about it.

Some Other Projects' Status

carol: openorb is not currently in JPackage; jacorb is not packaged and has 
many dependencies of its own.

joram: requires kjoram

kjoram: unknown/obsolete version of kxml---this should be updated to a more 
recent version, if possible; midpapi.jar means that all of wireless toolkit 
needs packaging (big job).

--
Sincerely,

David Walluck
<david@xxxxxxxxxxxxxxxxxx>

--- Begin Message ---

• Subject: Re: [architecture] Re: JPackages and ObjectWeb
• From: David Walluck <david@xxxxxxxxxxxxxxxxxx>
• Date: Tue, 27 Jan 2004 10:47:21 -0500

Emmanuel Cecchet wrote:

David,

I just figured out that you already did a rpm package for C-JDBC. Thanks a lot !

I cannot say with certainty that the package is at this time is 100% complete. Since we do not have a "testing" repository, the package is certainly there for people who want to say to me "Hey, when I download the package from objectweb.org, file `X' is included, and you forgot to include it". In other words. I would love if people test and send any bug reports.

Goulven Le Jeune (or anyone familar with jonas) can attest that even the current package of jonas is not complete. Sometimes these things take a lot of time. The netbeans package has been in development by someone at Sun for the good part of a year.

I will send an update later today detailing the packages that have been built so far, and what needs to be done.

How do we proceed with new versions? Do we send you an email or is there any process to generate new rpms automatically from the previous version?

Normally, we host the packages from our site. If you can set it up to automatically CC to jpackage-discuss when a release is made, then hopefully someone will see it and build a new package.

We do this the other way around too. I know that our argouml rpm announcement are automatically pushed to the argouml mailing list.

Is it ok to host the rpms on the ObjectWeb GForge as part of the projects distribution files?

We already do that for some projects (notably jakarta, jedit, fastutil). I'd prefer if we hold off for now on any public announcement until someone from each individual project can sign off as to the quality of the individual packages.

Last thing, is it possible to set the category (or categories?) in which the software can be found on http://www.jpackage.org/? I would suggest that C-JDBC is assigned to the 'Database' group.

To set the category (you're probably talking about the ones you see in "(choose your group)" box), all I have to do is rebuild the rpm with that group set and it will be automatically listed in that section. I will do this later today. Also, I'd be interested in any difference between the rpms and the binary releases on objectweb.org. This will help to catch any problems.

--
Sincerely,

David Walluck
<david@xxxxxxxxxxxxxxxxxx>

Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---

Attachment: signature.asc
Description: OpenPGP digital signature