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
