[Pkg-parrot-devel] New version of parrot package is in mentors

[Dominique Dumont]

Le mercredi 6 avril 2011 14:15:51, Jeremiah Foster a écrit :
> > Is it truly necessary for these packages to include the full version
> > number as opposed to simply the major release number (or even just
> > excluding the final part and using libparrot-3.x). If either of these is
> > possible, it would create a more stable and maintainable package which
> > would not require manual review quite so often.
> 
> There are a bunch of reasons why the version number in Debian packages is
> the way it is, and that the entire number is there. The version number
> allows the package management system (APT) to update to the correct, most
> recent version, for example. 

Hmm, you would be right if Kyle was mentioning '3.x' as being the package 
version. In libparrot's case, '3.x' is part of the package *name*. And the 
package file is libparrot3.0.0_3.0.0-1_amd64.deb

The point between soname and package name is explained there:

http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-
runtime

So the actual question (for Allison) is: 
- will next parrot lib release have  symbols removed or with changed signature 
since 3.0.0 ?

If not, the soname of libparrot should not change and the libpackage name 
should not change.

That said, having '3.0.0' in the package name will lead to confusion. Hence 
Kyle's suggestion to have only '3' (or may be '3.x') in the package name.
All depends on the evolution of libparrot ABI.

> > As a side note, Rakudo and Rakudo star both have expected releases this
> > month as well. It is probably worth knowing the version of Parrot that
> > these releases will require. I believe that users would greatly benefit
> > from a rakudo-star package in Debian and this will mean a dependency on
> > an updated version of Parrot.
> 
> Making sure Parrot and the Rakudos are in good shape for Debian is crucial.
> Collaboration is the keyword here (as in all Debian packages). If there is
> a team or a loose group around parrot packaging then that burden can be
> shared - like in the Debian perl group. It is considered bad form to
> upload NMUs however and I'm sure that is something that everyone wants to
> avoid. 
> 
> Is there a formal team around parrot that people can join to contribute? An
> alioth page or similar?

There's https://alioth.debian.org/projects/pkg-parrot/

I've tried to join (as ddumont-guest) but got no reply from its admin. I guess 
that upstream work keeps them quite busy ;-)

One thing is not clear is whether Debian package files should be archived on 
alioth or on upstream CVS. 

All the best


Dominique
--
http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/
http://www.ohloh.net/accounts/ddumont     -o- http://ddumont.wordpress.com/