Re[2]: project vision

Hello Paul,

Wednesday, April 13, 2005, 5:41:34 PM, you wrote:


>> In order to form vision of this project I would like to call attention
>> to mine.
>> 
>> General idea of the project:
>> 
>> jRPM is a package management system based on rpm packages written in
>> java. It provides pure java implementation or integration with native
>> rpm if available.
>> 
>> Key features:
>>  - resolves dependencies automatically
>>  - provides information from different kinds of package sources
>>  - gui (as there are mostly console programs)
>>  - searches for required packages in the net and downloads it
>>  - downloads manager

PN> Sounds like you're looking at a depsolver rather than an rpm impl.  Cf
PN> yum vs rpm and apt vs dpkg.  I'd recommend getting the core jrpm library
PN> be only dealing with packages and rpmdb, then letting other apps deal
PN> with repos, etc.
I have no objection. But if you are writing a library you should take
into consideration how it will be used.

PN> I'd say waht you're looking for should be written on top of jrpm not
PN> core to it.
As every linux distribution based on rpm has its' own depsolver, I
think original rpm doesn't provide all required features. So, why
not implement it in jRPM? Of course, the core should be written first,
but it is better to aim something greater :)


What is your vision of jrpm, what are the features it should provide,
how it will be used?



-- 

 Nikita



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click