builddep should be installed with --no-recommends
Bug #1473520 reported by
Thomi Richards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When installing a builddep with the builddeps phase, mojo should specify '--no-recommends' to apt. Otherwise, when installing 'bzr' as a build-dep, we end up installing all sorts of stuff, including (for example) gnome-keyring.
Related branches
lp:~mthaddon/mojo/no-recommends-1473520
- Barry Price: Approve
-
Diff: 27 lines (+4/-2)2 files modifieddocs/mojo/readme.md (+2/-0)
mojo/contain.py (+2/-2)
Changed in mojo: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Thinking about this some more...
I guess changing this now will likely break several existing mojo specs.
That's clearly not a good idea. Perhaps we can add an option to the
builddeps phase that controls whether or not --no-recommends is passed to
apt? It could even be documented as a sensible default for new specs...
something like:
builddeps packages= bzr,make, python- yaml install_ recommends= no
Thougths?
--
Thomi Richards
<email address hidden>