If my understanding is correct (might not be), the tarball should be ALMOST equivalent to:
rakudobrew build moar 2016.01.1 # Install rakudo 2016.01.1 rakudobrew global 2016.01.1 # Make this the default rakudobrew build panda # Build panda for this rakudo panda install Task::Star # Get the latest Task::Star, needs --force to do again I just did these steps on my Debian machine with no problems. The main issue I can think of is the last step -- installing Task::Star installs the current version of all the packages, whereas the tarball rakudo-star release includes a specific version of each of the Star modules. If someone updates SVG then this will get the LATEST, not the one in the official release. I think this is a weakness of the versioning system -- ideally you'd be able to do something like "panda install Task::Star=2016.01" and get the exact same thing. I see Moritz replied to this also saying that the tarball is the way to go. I'd love to know what I'm missing out on by doing it this way. --Brock On Thu, Feb 4, 2016 at 7:26 AM, James E Keenan <jk...@verizon.net> wrote: > On 02/03/2016 10:48 PM, Brandon Allbery wrote: > >> On Wed, Feb 3, 2016 at 10:30 PM, James E Keenan <jk...@verizon.net> >> wrote: >> >> I am evidently confused as to the relationship, if any, between the >>> 'rakudobrew' utility and the Rakudo::Star distribution. >>> >> >> >> In short: rakudobrew is for the folks who want to track the rapid >> development of Rakudo. Star is for folks who want something stable in >> order >> to play with the language, and includes the Task::Star ecosystem. As Star >> was cut earlier today, it's based on the rakudo that was current earlier >> today (and still fairly current as there haven't been many commits in the >> past few hours). >> >> It's more or less the difference between a Python or Perl 5 release, and >> installing either from git HEAD. rakudobrew builds from HEAD; Star is a >> release, which happens to be close to HEAD at the moment because it was >> just created. HEAD will keep moving; Star will stay stable for a while >> (used to be monthly, but they're considering releasing less often now) >> before the next release. >> >> > So, to clarify: If I want to get this week's release of Rakudo Star on, > say, Linux, I have to download this tarball: > > http://rakudo.org/downloads/star/rakudo-star-2016.01.tar.gz > > ... and build from source -- correct? I cannot use rakudobrew for Rakudo > Star -- correct? > > > Thank you very much. > Jim Keenan >