[Pkg-parrot-devel] sound distribution practices

Guy Hulbert gwhulbert at eol.ca
Sun Apr 8 13:29:46 UTC 2012


On Sun, 2012-08-04 at 15:23 +0200, Alessandro Ghedini wrote:
> On Sat, Apr 07, 2012 at 09:08:21PM -0400, Andrew Whitworth wrote:
> > What if we did something like bundling?
> 
> Isn't this what Rakudo Star does? AFAICT the Star "distribution" is nothing more
> than a bundle of rakudo + nqp + parrot + some Perl 6 modules, which may be nice
> from a end user POV, but it's plain wrong from a distribution one. We (Debian)
> have different source packages for Parrot, Rakudo and NQP (which are managed by
> two diffent teams) so that we can handle issues and changes separately without
> the need to rebuild all of them every time one needs to be changed. Bundling

All you need to do is to coordinate with the parrot team on the version
to build.  From what I have read (as a potential end-user of Rakudo on
Debian) in this thread, failure to do this will make any packaging
efforts completely pointless.

> them together would just make the Parrot and Rakudo packages more dependant on
> each other... which is exactly what we are trying to avoid. Also see the third
> paragraph of [0]. Btw, this also applies to NQP bundling full source of
> libtommath and dyncall.
> 
> (/me being one of the Debian Rakudo maintainers)
> 
> Cheers
> 
> [0] http://wiki.debian.org/UpstreamGuide#Pristine_Upstream_Source
> 
> _______________________________________________
> Pkg-parrot-devel mailing list
> Pkg-parrot-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-parrot-devel
-- 
--gh




More information about the parrot-dev mailing list