Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-09-15 Thread Ryan Niebur
Hi Allison,

On Tue, Sep 01, 2009 at 09:16:52PM -0700, Allison Randal wrote:
> Ryan Niebur wrote:
>>
>> ya. preparing an experimental upload would be great. Do you want to
>> wait for the September release or package the SVN version?
>
> Let's wait for the releases. Parrot and Rakudo are carefully sync'd at  
> release points, but there's no guarantee of compatibility at random  
> SVN/git revisions.
>
>> adding experimental to the sources.list and running "apt-get install
>> -t experimental rakudo" is easier than downloading .debs from alioth,
>> and it means that it's more official (because it's actually in Debian
>> repos). other than that, I don't see the difference.
>
> I talked some with Patrick about plans for Rakudo releases. It sounds  
> like it'll be useful to have the 1.6 (maybe 1.8) and 2.3 releases of  
> Parrot in experimental. Rakudo packages could be in experimental around  
> Parrot 1.6, (maybe 1.8,) 2.0 (January), and 2.3 (April), then aim for  
> Rakudo in Debian unstable around Parrot 2.6 (July).
>

as I'm sure you already know, parrot 1.6 is now released, so how about
an upload to experimental? :)

Cheers,
Ryan

-- 
_
Ryan Niebur
ryanrya...@gmail.com


signature.asc
Description: Digital signature


Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-09-01 Thread Allison Randal

Ryan Niebur wrote:


ya. preparing an experimental upload would be great. Do you want to
wait for the September release or package the SVN version?


Let's wait for the releases. Parrot and Rakudo are carefully sync'd at 
release points, but there's no guarantee of compatibility at random 
SVN/git revisions.



adding experimental to the sources.list and running "apt-get install
-t experimental rakudo" is easier than downloading .debs from alioth,
and it means that it's more official (because it's actually in Debian
repos). other than that, I don't see the difference.


I talked some with Patrick about plans for Rakudo releases. It sounds 
like it'll be useful to have the 1.6 (maybe 1.8) and 2.3 releases of 
Parrot in experimental. Rakudo packages could be in experimental around 
Parrot 1.6, (maybe 1.8,) 2.0 (January), and 2.3 (April), then aim for 
Rakudo in Debian unstable around Parrot 2.6 (July).


Allison



--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-08-31 Thread Ryan Niebur
Hi,

On Mon, Aug 31, 2009 at 05:33:47PM -0700, Allison Randal wrote:
> Ryan Niebur wrote:
>> please keep the ITP bug CCed.
>
> Apologies, was replying from my phone.
>

no problem.

>> On Mon, Aug 31, 2009 at 03:45:07PM -0700, Allison Randal wrote:
>> they're actually in unstable. anyways, I need the unreleased versions
>> of parrot (more recent than 1.5.0 even). I'm using r40789 from SVN
>> locally.
>
> Now that I have real internet access again... the automated notice was  
> that 1.4 packages were migrated to "testing". So, yes, not relevant to  
> what you're looking for.
>
> We only package the stable releases because the intermediate monthly  
> releases are for development testing, not for broader use. I'm willing  
> to package some monthly releases between now and Parrot's next stable  
> release (2.0 in January), just to be absolutely sure that Rakudo  
> packages can enter unstable at the same time as Parrot 2.0. As long as  
> it's understood that the experimental packages don't supersede the 1.4  
> packages in unstable/testing, and won't ever migrate to unstable or  
> testing. They're just throwaway packages for Rakudo testing.
>

ya. preparing an experimental upload would be great. Do you want to
wait for the September release or package the SVN version?

> But, it really boils down to a question of whether you have Rakudo users  
> testing Debian experimental. If not, then it makes more sense to put the  
> intermediate packages up on alioth.
>

adding experimental to the sources.list and running "apt-get install
-t experimental rakudo" is easier than downloading .debs from alioth,
and it means that it's more official (because it's actually in Debian
repos). other than that, I don't see the difference.

Thanks,
Ryan

-- 
_
Ryan Niebur
ryanrya...@gmail.com


signature.asc
Description: Digital signature


Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-08-31 Thread Allison Randal

Ryan Niebur wrote:

please keep the ITP bug CCed.


Apologies, was replying from my phone.


On Mon, Aug 31, 2009 at 03:45:07PM -0700, Allison Randal wrote:
they're actually in unstable. anyways, I need the unreleased versions
of parrot (more recent than 1.5.0 even). I'm using r40789 from SVN
locally.


Now that I have real internet access again... the automated notice was 
that 1.4 packages were migrated to "testing". So, yes, not relevant to 
what you're looking for.


We only package the stable releases because the intermediate monthly 
releases are for development testing, not for broader use. I'm willing 
to package some monthly releases between now and Parrot's next stable 
release (2.0 in January), just to be absolutely sure that Rakudo 
packages can enter unstable at the same time as Parrot 2.0. As long as 
it's understood that the experimental packages don't supersede the 1.4 
packages in unstable/testing, and won't ever migrate to unstable or 
testing. They're just throwaway packages for Rakudo testing.


But, it really boils down to a question of whether you have Rakudo users 
testing Debian experimental. If not, then it makes more sense to put the 
intermediate packages up on alioth.


Allison




--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-08-31 Thread Ryan Niebur
please keep the ITP bug CCed.

On Mon, Aug 31, 2009 at 03:45:07PM -0700, Allison Randal wrote:
> Last I heard (by automated notice), parrot 1.4 packages are already in 
> experimental, though I didn't check to make sure.

they're actually in unstable. anyways, I need the unreleased versions
of parrot (more recent than 1.5.0 even). I'm using r40789 from SVN
locally.

Cheers,
Ryan

-- 
_
Ryan Niebur
ryanrya...@gmail.com


signature.asc
Description: Digital signature


Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-08-31 Thread Ryan Niebur
On Mon, Aug 31, 2009 at 03:40:34PM +0200, Marc 'HE' Brockschmidt wrote:
> Ryan Niebur  writes:
> >  Rakudo Perl is an implementation of the Perl 6 specification that
> >  runs on the Parrot virtual machine.
> >
> > I won't be able to upload this for a while, because previous to the
> > current git version the build system didn't work with system installed
> > parrot. parrot and rakudo release go together (monthly), but the
> > debian maintainer of parrot only uploads the "stable" releases. So I
> > have to wait for the next stable version of parrot to be released and
> > uploaded to debian, and then for the corresponding version of rakudo
> > to be released. So it will probably be a few months...
> 
> Would it be possible to put a current parrot build into experimental?
> 

ask allison, not me :). anyways, if we were going the experiemental
route, we'd either have to put rakudo from git and parrot from svn, or
wait until the septemeber releases of both of them. either of which I'd
be happy to do, and I have rakudo + parrot packages building from git/svn.

so Allison, what's your opinion?

-- 
_
Ryan Niebur
ryanrya...@gmail.com


signature.asc
Description: Digital signature


Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-08-31 Thread Marc 'HE' Brockschmidt
Ryan Niebur  writes:
>  Rakudo Perl is an implementation of the Perl 6 specification that
>  runs on the Parrot virtual machine.
>
> I won't be able to upload this for a while, because previous to the
> current git version the build system didn't work with system installed
> parrot. parrot and rakudo release go together (monthly), but the
> debian maintainer of parrot only uploads the "stable" releases. So I
> have to wait for the next stable version of parrot to be released and
> uploaded to debian, and then for the corresponding version of rakudo
> to be released. So it will probably be a few months...

Would it be possible to put a current parrot build into experimental?

Marc
-- 
BOFH #254:
Interference from lunar radiation


pgp2TW3FRCSTi.pgp
Description: PGP signature


Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot

2009-08-31 Thread Ryan Niebur
Package: wnpp
Owner: Ryan Niebur 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: rakudo
  Version : "2009-08" aka PDX (will probably use 0.1~2009-08-1 for the 
package version)
  Upstream Author : The Rakudo Team
* URL : http://rakudo.org/
* License : Artistic License 2.0
  Programming Lang: Parrot
  Description : implementation of Perl 6 for Parrot

 Rakudo Perl is an implementation of the Perl 6 specification that
 runs on the Parrot virtual machine.

I won't be able to upload this for a while, because previous to the
current git version the build system didn't work with system installed
parrot. parrot and rakudo release go together (monthly), but the
debian maintainer of parrot only uploads the "stable" releases. So I
have to wait for the next stable version of parrot to be released and
uploaded to debian, and then for the corresponding version of rakudo
to be released. So it will probably be a few months...

-- 
_
Ryan Niebur
ryanrya...@gmail.com


signature.asc
Description: Digital signature