Feature #157
Standalone gem packages
| Status: | New | Start date: | 10/05/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | OpenNebula Core | |||
| Target version: | - | |||
| Resolution: | Addon: | |||
| Story points | - | |||
| Velocity based estimate | - |
Description
Create gem packages to install tools (OCA, EC2, OCCI) and its requirements.
They should work even if OpenNebula server is not installed in the machine.
History
Updated by Javi Fontan over 2 years ago
- File oca_gem.tar.gz added
- Category set to OpenNebula Core
- Assignee set to Javi Fontan
Initial version of OCA and CLI gem.
- Commands lack
require 'rubygems'to work - Gem does not install binaries in path
- Missing metadata and license
Updated by Ruben S. Montero almost 2 years ago
- Target version set to Release 2.0
Updated by Claude Noshpitz over 1 year ago
Gem packaging may imply changes in the way the CLIs find their libraries. The ONE_LOCATION env variable does not really help, in particular when the gem contains just client code and there's no other ONE installation.
It may be worthwhile to have the CLIs check for a fixed location that would exist (only) for a gem install if ONE_LOCATION is not set, for example
$: << "#{File.dirname(FILE)}/../lib"
Updated by Daniel Molina over 1 year ago
- Target version deleted (
Release 2.0)
Updated by Ruben S. Montero 9 months ago
- Target version set to Release 3.0
Updated by Ruben S. Montero 9 months ago
- Target version deleted (
Release 3.0)