[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#249570: openjade1.3 should provide openjade

On Nov  9, Yann Dirson (ydirson@altern.org) wrote:
 > On Tue, Nov 09, 2004 at 01:00:08AM +0100, Peter Eisentraut wrote:
 > > The current openjade packaging situation has a bit of a problem.  The 
 > > "openjade" package is a dead development snapshot which has major 
 > > usability problems and no fixes in sight.  The really useful version is 
 > > hidden as "openjade1.3", which some packages have not even listed in 
 > > their dependencies.  The popcon numbers show that users are clearly 
 > > mislead.
 > > 
 > > I propose that the "openjade" package becomes 1.3 (should be 1.3.3 by 
 > > now) and that the 1.4 snapshot gets moved to experimental, an 
 > > "openjade1.4" package, or be removed altogether.

I'm the openjade maintainer, as well as jade and opensp.

I think the best approach would be to create an openjade1.4 package, keep the
openjade1.3 package, then transform the openjade package to one that simply
depends on openjade1.3.  This is analogous to the relationship between gcc,
gcc-3.3 and gcc-3.4.

 > I would have supported this approach at 100% if package openjade would never
 > have been 1.4devel.  Doing so at this point would cause problems for people
 > using it.

 > However, maybe there are not so many people relying on 1.4devel feature ?
 > Hard to say, and definitely not to be tested before we release sarge :)

Jade (yes, the ancient version) is still used far more widely than both of the
versions of openjade combined.  So, probably not many people rely on 1.4devel
features.  Of course, I agree on the second point.

 > What can still be achieved IMHO before we release sarge would be to make
 > sure that all packages listing openjade in their deps have openjade1.3 first
 > as an alternative.


Neil Roeth

Reply to: