Feature #157

Standalone gem packages

Added by Javi Fontan almost 10 years ago. Updated over 6 years ago.

Status:ClosedStart date:10/05/2009
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Core & System
Target version:Release 4.0
Resolution:fixed Pull request:

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.

oca_gem.tar.gz (622 Bytes) Javi Fontan, 10/05/2009 11:09 PM

Associated revisions

Revision 20aab344
Added by Javi Fontan over 6 years ago

request #157: Add first version of rubygems generator

Executing share/reubygems/generate ir will create gems for OCA and CLI.
The new gems will be copied to the source code root directory.

Modify DEFAULTS, TEMPLATE and GEM_DESCRIPTION constants to modify or
add new gems.

Revision f7b204e6
Added by Javi Fontan over 6 years ago

request #157: delete of debugging code

Revision 78b34667
Added by Javi Fontan over 6 years ago

request #157: add copyright notice

Revision 14211ce0
Added by Javi Fontan over 6 years ago

request #157: add rubygems generation to scons script

Revision 72df7a3b
Added by Javi Fontan over 6 years ago

request #157: typo

Revision e9ec2ce6
Added by Javi Fontan over 6 years ago

request #157: add NOTICE and LICENSE files

Revision 88bb97ca
Added by Tino Vázquez over 2 years ago

Merge pull request #157 from n40lab/one-5.2

Fix B#4928 import vcenter networks with same name in different clusters

History

#1 Updated by Javi Fontan almost 10 years ago

  • File oca_gem.tar.gz added
  • Category set to Core & System
  • 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

#2 Updated by Ruben S. Montero over 9 years ago

  • Target version set to Release 2.0

#3 Updated by Claude Noshpitz about 9 years 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"

#4 Updated by Daniel Molina almost 9 years ago

  • Target version deleted (Release 2.0)

#5 Updated by Ruben S. Montero about 8 years ago

  • Target version set to Release 3.0

#6 Updated by Ruben S. Montero about 8 years ago

  • Target version deleted (Release 3.0)

#7 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Feature to Request

#8 Updated by Ruben S. Montero over 6 years ago

  • Tracker changed from Request to Feature
  • Target version set to Release 4.0

#9 Updated by Javi Fontan over 6 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF