I have a couple of feature suggestions based on a private discussion with Klaus about packaging gems ... In the cases where gem are only available from upstream via a git tag rather than from rubygems.org (e.g. vagrant), gem2rpm only works with these extra steps: git clone git://github.com/mitchellh/vagrant.git cd vagrant gem build vagrant.gemspec gem2rpm vagrant-1.5.0.dev.gem > vagrant.spec It would be nice to automate this, given that tar_scm already builds the tarball from git. Would it be worth extending gem2rpm so that it can also operate on a given directory containing an unpacked gem, or a tarball? Or maybe it would be even nicer to build a gem2rpm source service which can automatically generate a .spec or update an existing .spec? -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org