Merge lp:~allenap/maas/offline-more into lp:maas/trunk
| Status: | Merged |
|---|---|
| Approved by: | Gavin Panella on 2012-09-24 |
| Approved revision: | 1063 |
| Merged at revision: | 1063 |
| Proposed branch: | lp:~allenap/maas/offline-more |
| Merge into: | lp:maas/trunk |
| Diff against target: |
40 lines (+8/-8) 1 file modified
Makefile (+8/-8) |
| To merge this branch: | bzr merge lp:~allenap/maas/offline-more |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| John A Meinel | Approve on 2012-09-25 | ||
| Diogo Matsubara (community) | 2012-09-24 | Approve on 2012-09-24 | |
|
Review via email:
|
|||
Commit Message
make offline=true <target> now keeps buildout and virtualenv off the network for all targets.
Previously there was a build-offline target that permitted an offline build only. This is a more general solution.
| John A Meinel (jameinel) wrote : | # |
It seems a little funny that the way it is defined you can do:
make offline=False
And it will build offline. However, I don't care a ton about that.
It seems more like something that you would want to set up per-site rather than something you have to think about passing to make. However, it is certainly better than not having it at all.
I wonder about doing:
buildout := bin/buildout buildout:
| Gavin Panella (allenap) wrote : | # |
> make offline=False
Yeah, that is a bit of a wart :-/
> buildout := bin/buildout buildout:
We'd still need to do something about virtualenv, but that seems okay, assuming buildout will cope with the empty string there.
In the fullness of time I'd like to remove buildout and settle with just one virtualenv. buildout has sucked away so much time compared to the benefits it brings. It tries to do too much but has more edge cases than monoclinic sulphur.
| John A Meinel (jameinel) wrote : | # |
I would tend to agree that buildout doesn't work quite as well as advertised in real situations.


Looks good!