Still downloading drubuntu-6.x-9.10-beta1 into the workspace.

drubuntu-boostrap.sh is currently specifying that it is using 6.x, so is pulling the recommended 6.x version of the script. I think rather than grab the recommended version of the script, it would be better if the script pulled down it's own tagged version from CVS. That way if a user wants to standardize multiple machines on a given version of drubuntu, they won't have to fight against CVS tags.

Comments

owen barton’s picture

owen barton commented
Status: Active » Needs review

Thanks for trying this out so quickly, and posting the issues!

We weren't specifying the 6.x release (that is for initially downloading Drush - see #1011368: Instructions on project page don't work (SimpleXML error)), it was Drush that still defaults to downloading 6.x releases when outside a core (I guess we had better fix that too!). For now, I think the easiest fix is to cut a 6.x tag (identical to the 7.x tag), which is what I have just done. You will get an interactive prompt until the update xml refreshes to reflect the recommended status (in a few minutes or hours).

Using the CVS tag to pull the associated release is fairly tricky, as CVS versions each file differently, and will only fill in a $name keyword for tags on checkout (so our wget would not pick it up). I think the way to go is to pass in the recommended version on the bootstrap command on the project page, and people can tweak that as needed.

Grayside’s picture

Grayside commented
Component: Code » Documentation
Status: Needs review » Reviewed & tested by the community

That works. I haven't been using that snippet, instead I've been downloading the actual recommended tarball and running the install script. So the followup download of drubuntu has been strangely redundant ;)

I suggest the front page also be reformatted slightly, through an Installation heading above that snippet.

You could also cheat:

function drubuntu_version() {
  return '7.10-beta2';
}

But that's not fun.

I was just thinking to myself how fantastic it was that you kept working on this throughout the holidays. I'm looking forward to setting this up as my full-time development environment in a week, so the faster I can push in the next few days, the fewer my frustrations will be.