Moving giftwrap under the Blue Box Group org

Moving giftwrap to Blue Box as we have been maintaining it.
This commit is contained in:
Craig Tracey 2014-11-18 15:06:09 -05:00
parent 87509297f7
commit 47ee5cc1d7
2 changed files with 14 additions and 13 deletions

View File

@ -14,8 +14,9 @@ Inspired by some of the work I had done to create [omnibus-openstack](https://gi
With all of this in mind, it seemed to me that we already had all of the information that we already needed to create system-native (ie. rpm, deb) packages that had already been tested with the Gerrit CI infrastructure. Hence, giftwrap. With all of this in mind, it seemed to me that we already had all of the information that we already needed to create system-native (ie. rpm, deb) packages that had already been tested with the Gerrit CI infrastructure. Hence, giftwrap.
### Status Status
[![Build Status](https://api.travis-ci.org/cloudcadre/giftwrap.png)](https://api.travis-ci.org/cloudcadre/giftwrap) ------
[![Build Status](https://api.travis-ci.org/blueboxgroup/giftwrap.png)](https://travis-ci.org/blueboxgroup/giftwrap)
Usage Usage
===== =====
@ -24,29 +25,29 @@ Usage
$ giftwrap -h $ giftwrap -h
Dependencies Dependencies
============ ------------
* `Vagrant` * `Vagrant`
* `fpm` * `fpm`
Development Development
=========== -----------
$ git clone git@github.com:cloudcadre/giftwrap.git $ git clone https://github.com/blueboxgroup/giftwrap.git
$ vagrant up $ vagrant up
Testing Testing
======= -------
$ make test $ make test
Supports Supports
======== --------
* Jinja2 templating - change your build by changing variables; not your manifest * Jinja2 templating - change your build by changing variables; not your manifest
* versioned paths - this allows you to run services side by side; easing the upgrade process. * versioned paths - this allows you to run services side by side; easing the upgrade process.
How It Works How It Works
============ ------------
giftwrap is pretty simple. The basic flow is something like this: giftwrap is pretty simple. The basic flow is something like this:
1. Create a YAML manifest with the packages you would like to build. See sample.yml 1. Create a YAML manifest with the packages you would like to build. See sample.yml
2. Run: 2. Run:
@ -62,13 +63,13 @@ giftwrap is pretty simple. The basic flow is something like this:
9. An [fpm](https://github.com/jordansissel/fpm) package will be built from the intersection of the python install and system dependencies 9. An [fpm](https://github.com/jordansissel/fpm) package will be built from the intersection of the python install and system dependencies
TODO TODO
==== ----
* Provide option for source removal; package only the executables * Provide option for source removal; package only the executables
* Allow for additional pip dependencies, alternate pip dependency versions, and even user-defined pip dependencies * Allow for additional pip dependencies, alternate pip dependency versions, and even user-defined pip dependencies
* Allow for additional/alternate system package dependencies * Allow for additional/alternate system package dependencies
License License
======= -------
| | | | | |
|:---------------------|:---------------------------------------------------| |:---------------------|:---------------------------------------------------|
| **Authors** | John Dewey (<john@dewey.ws>) | | **Authors** | John Dewey (<john@dewey.ws>) |

View File

@ -4,9 +4,9 @@ version = 0.3.0
summary = giftwrap - A tool to build full-stack native system packages. summary = giftwrap - A tool to build full-stack native system packages.
description-file = description-file =
README.md README.md
author = John Dewey author = Craig Tracey
author-email = jodewey@cisco.com author-email = craigtracey@gmail.com
home-page = https://github.com/cloudcadre/giftwrap home-page = https://github.com/blueboxgroup/giftwrap
include_package_data = True include_package_data = True
classifier = classifier =
Intended Audience :: Information Technology Intended Audience :: Information Technology