[Pkg-parrot-devel] Package for parrot-3.6.0 status - work in progress

[Dominique Dumont]

On Thursday 28 July 2011 16:11:29 Allison Randal wrote:
> Great. Where can I get the latest Rakudo packaging to test that the
> [perlapi] changes we make in the Parrot packages solve the problem for 
Rakudo?

Latest rakudo provides only rakudo 0.1~2011.04. This one is available in 
Debian unstable. 

On the other hand, the fix consists in making sure that parrot binary package 
depends on perlapi-5.12.4 (matching the perl used to build parrot). So a 
recent rakudo package is not required to progress on this topic.

> > - make sure that parrot-devel and libparrot-dev are not required to
> > install rakudo.
> > 
> > We'll need people better knowing parrot to handle the second issue.
> 
> Do you have specific failures that are currently preventing rakudo from
> installing without depending on parrot-devel and libparrot-dev? 

That's quite easy to find out:

$ sudo dpkg --force-depends --remove parrot-devel
[ snip ]
$ perl6
"load_bytecode" couldn't find file 'P6Regex.pbc'
current instr.: '' pc -1 ((unknown file):-1) (:7613)
called from Sub 'perl6;Perl6;Compiler;main' pc 331869 (src/gen/perl6-
grammar.pir:17325)
... call repeated 1 times

On the other hand, a forced removal of libparrot-dev looks fine:

$ sudo dpkg --force-depends --remove libparrot-dev 
[ snip ]
$ perl6
> say "hello";
hello
> exit;

> There are a variety of different tools, but
> our options basically boil down to:
> 
> * make our git repository a branch of the full set of parrot changes,
> with the tarballs tagged over existing release tags, and our debian/
> directory added on top
> 
> * make our git repository a log of debian releases (and relevant parrot
> tarballs), with our debian/ directory included
> 
> * make our git repository a record of our debian/ directory only
> 
> I'm inclined to go with the second, as that gives us the best record of
> history of Debian Parrot packages, without requiring everyone who
> contributes to the Debian packaging to cope with the full complexity of
> Parrot development.

Usual packaging workflow does not require debian-pkg-parrot member to use 
upstream-parrot git as we use tarballs released by upstream project (with git-
import-orig)

> We have more details to decide on workflows, but deciding on the base
> contents of the repository is the first step.

I'm a git newbie so I don't really know what theses options means for the 
workflow.

However, to encourage teamwork at parrot packaging level, you should make sure 
that:
- all debian-pkg-parrot members can push to debian git
- all debian-pkg-parrot members work with debian git OR any modif done to 
debian package file in upstream-parrot git can be merged in debian git using 
git.


Hope this helps

Dominique
--
http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/
http://www.ohloh.net/accounts/ddumont     -o- http://ddumont.wordpress.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-parrot-devel/attachments/20110728/1a16cc98/attachment.pgp>