Closed Bug 1164812 Opened 11 years ago Closed 11 years ago

mach mercurial-setup handling of reviewboard doesn't mark the version-control-tools repo as needing update

Categories

(MozReview Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(1 file)

In mach mercurial-setup, when calling prompt_external_extension(), you can either: * not pass in a path - in which case the version-control-tools/hgext/<extension-name>/ is used, and the version-control-tools repo marked as needing a clone/update * pass your own path - in which case the version-control-tools repo isn't cloned/updated The intention for the second case, was for extensions that do not live in the version control tools repo, so would have their own repo cloned/updated separately. However for reviewboard, since we have to use client.py specifically (rather than version-control-tools/hgext/reviewboard/*), the call to prompt_external_extension() has been made with the path set. This means that if the reviewboard extension was the only one the user chose to accept when prompted, we won't clone (or update if already cloned) the version-control-tools repo. Options: 1) Remove external extension support entirely (once bug 978514 lands there will be no external extensions referenced by mach mercurial setup): * rename prompt_external_extension() to prompt_vct_extension() * make 'path' relative to version-control-tools repo root * set self.update_vcs_tools to true regardless of the value of path 2) Leave external extension support in, but set self.update_vcs_tools to true in prompt_external_extension(), regardless of the value of path
I'd like to leave external extension support in because there are a number of Facebook extensions that should arguably be in mach mercurial-setup. It's a good idea for v-c-t to always be up to date. We should just do the update unconditionally.
Assignee: nobody → emorley
Status: NEW → ASSIGNED
Attachment #8607156 - Flags: review?(gps)
Attachment #8607156 - Flags: review?(gps) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Developer Services → MozReview
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: