[ANN] gem2tgz 1.0

cycojesus · 02-22-2011, 09:36 PM

Slackers worldwide, I give you gem2tgz.

<Here I'd bury debian under a smelly pile of trolls' feces but let's not for now, however tempting it is...>

in 176 lines of shell gem2tgz makes Slackware and Ruby's gems become BFF by making packages out of gems so that Slackware know about them and can manage them like any other packages.

Code:

Usage: /usr/bin/gem2tgz <options>
Options:
	-a | --backup | --all-locals
		Generate packages for ALL gems installed locally

	-g | --gem <name>
		gem to package [no default]
	-v | --version <x.x.x>
		Package a specific version [default: latest]
	-t | --tag <tag>
		Set a specific tag for the package's name [default: gem2txz]
	-n | --nodeps
		Do not build packages of dependencies [default: package all dependencies]
	-i | --install
		Install the package [default: no]
	-o | --output <dir>
		Directory where the resulting package will be [default: /tmp]

	-h | --help
		What you're reading at this very moment

After semi-extensive testing here it looks pretty solid to me and time has come to release it into the wild, so:
- here's the github repository: https://github.com/cycojesus/gem2tgz
- here's a ready-made package: http://cycojesus.free.fr/files/gem2t...arch-1cyco.txz

Please enjoy and any/all feedback is welcome

rworkman · 02-22-2011, 11:22 PM

If it's not too much trouble, how about doing up everything necessary for a SlackBuilds.org submission similar to cpan2tgz?

On that note, probably it would be better to call this "gem2tgz" and implement the ability to compress using xz and perhaps others instead. That's (obviously) your call though.

cycojesus · 02-23-2011, 07:15 AM

Thanks. The first version was made around the same time Slackware moved to the .txz format so the name meant to reflect this change. Nevertheless I agree that Slackware still has a strong association with "tgz" and for consistency I'll rename (and edit the links here).

As for SBo, I'm an extensive user of it and I'll see to submit gem2tgz once I get github to serve a tagged archive. That could be the start of my contribution to SBo with those of my slackbuilds that are submittable (I tend to have scripts that pull directly from git|hg|svn|...)