preinstall packages for charms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| juju |
Wishlist
|
Unassigned | ||
| pyjuju |
Wishlist
|
Unassigned |
Bug Description
hooks can't be written in any language not already installed in bare cloud images.
We can fix this a number of ways... I prefer adding an optional 'preinstall_
Changed in juju: | |
status: | New → Confirmed |
Changed in juju-core: | |
status: | New → Confirmed |
tags: | added: production |
Changed in juju: | |
importance: | Undecided → Wishlist |
William Reade (fwereade) wrote : | #1 |
Changed in juju-core: | |
status: | Confirmed → Triaged |
importance: | Undecided → Wishlist |
Tim Penhey (thumper) wrote : | #2 |
So, if the install hook was written in bash, it may look something like:
#!/bin/bash
apt-get install -y ruby
call-install-
Can someone see if that works? Perhaps the script needs a path?
Mark Mims (mark-mims) wrote : | #3 |
Yeah, seemed to work fine with an install hook of
#!/bin/bash
apt-get -y install -qq ruby
exec hooks/install.rb
with the rest of the hooks written directly in ruby... tested with
lp:~mark-mims/charms/precise/ruby/trunk
which gives me a log like:
http://
could probably even do something like:
#!/bin/bash
apt-get -y install -qq ruby && ruby -x << EOF
puts "ruby stuff here"
EOF
but it'd be nice to have the ruby packages already installed before the install script is run.
Dave Cheney (dave-cheney) wrote : | #4 |
I think wishlist is the appropriate status, there are a lot of workarounds available and most of them aren't so horrid.
tags: | added: improvement |
Changed in juju-core: | |
importance: | Wishlist → Low |
Changed in juju-core: | |
importance: | Low → Wishlist |
affects: | juju-core → juju |
Now that hooks are serialized per-unit, "apt-get install" in "install" hooks shouldn't be a problem.