[Pkg-osg-devel] Project pkg-osg approved in Alioth

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Wed Jan 5 12:53:52 UTC 2011


On Wednesday 05 January 2011 13:27:18 Alberto Luaces wrote:
> In that case I would go further and use osg1, osg2, osg3... since API
> breakings like the one from 1.x to 2.x are not likely to happen so
> frequently. osg2 would group, for example, 2.4.x, 2.6.x, 2.8.x... since
> they are all source compatible.

OK, seems sensible.

> > But maybe it's not worth the effort, I don't know.  Or it's better to
> > maintain the stable package named generically "osg", with no versions
> > contained in the name, for some other reason.
> 
> Maybe we can do it lazily, only when the problem arises. Imagine that
> OSG 3.x is source incompatible with OSG 2.x and upstream's openflight or
> others are stuck with the older version for months or years. We can then
> craft a special package named osg2 for them to use and for their
> packages to be able to hit the testing/stable repositories.

That's fine for me, too.

Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>



More information about the Pkg-osg-devel mailing list