696243 - setup_development.py script for mozmill needs to be fixed

Status: RESOLVED FIXED

(Testing Graveyard :: Mozmill, defect)

Description

[Jeff Hammel]

bug 695846 moves mozrunner, etc, into the mozbase repo.  However, in general, you will need the development (master HEAD) versions of these packages to develop the master HEAD version of mozmill. setup_development, as it stands, can't really do this, so we need to make it do this or figure out some options.

Comment 1

[Jeff Hammel]

So a few options:

- we can have mozmill's setup_development.py checkout/pull the mozbase repo in some user-specified place and use its setup_development.py from there.  However, mozbase is a github repo.  This means the the pull will have to be from the read-only repository, or even if the repository is specified, you will have to type in your password.  This seems like maybe more trouble than its worth

- we can continue having setup_development.py but only work on jsbridge, mozmill, and mutt; However, you generally only have to run this once until the versions are bumped.  *AND* the time you need to run it -- right after you clone -- will not work, because in general you will need the HEAD of mozbase.  setup_develop.py becomes purely a way of avoiding typing 

for i in jsbridge mozmill mutt; do cd $i; python setup.py develop; cd ..; done

While it is nice to avoid this typing, the main point of mozmill's setup_develop.py is in fact to install dependencies *in the right order*. It will no longer really serve this end.  It could also be confusing since it will no longer do the right thing wrt to need mozbase changes

- we could eliminate mozmill's setup_develop.py.

we could also have an INSTALL.py script that will give you a basic setup with mozbase in a virtualenv and possibly provide its own setup_develop.py script as well that will only work in this controlled environment.

Note that the main point here is that master:HEAD (of mozmill) should in general be compatible with master:HEAD (of mozbase).  While this is a mozmill-specific issue, we will run into several things like this with things that depend on mozbase

Comment 2

[Jeff Hammel]

after talking with ahal, I think the short-term plan is to just have setup_development.py work for jsbridge, mozmill, and mutt.  We can reconsider this later.

Comment 3

[Jeff Hammel]

Attachment: eliminate things that no longer live here

its a bit of kicking the can, but sometimes you got to kick the can to get anywhere

Comment 4

[Andrew Halberstadt [:ahal]]

Comment on attachment 568672 [details] [diff] [review]
eliminate things that no longer live here

Review of attachment 568672 [details] [diff] [review]:
-----------------------------------------------------------------

r+

Comment 5

[Jeff Hammel]

pushed to master: https://github.com/mozautomation/mozmill/commit/9a8e899d5ce9854e8af6b2e437a3a7b531606938

We'll probably want to figure out what we really want to do at some point, but this is fine for now.