- When converting gem->rpm, turn 'rubygem-foo' provides into 'rubygem(foo)'
Adding the noreplace option to config files in the rpm spec template.
Python packages that are pinned to a specific version can not be packaged as .deb
When a compound spec is found, like tornado>=1.0,<=1.1 multiple entries will be added to the dependency list: tornado >= 1.0 and tornado <= 1.1 Because that seems to work for the debian dependency specification.
… if dependencies should be strictly versioned or allow iteration.
….html#s-depsyntax (= version) is valid and also that is sematically more correct than (>= version) and (<< version+1) because your +1 guess is just that, a guess.
…e found prefer order is "<=", "==", ">=" and next the version number.
use it as a glob. Fixes #202
This prevents the rpm install/update from overwriting local modifications to config files.
Fixed gem ~> version operator translated to rpm require.
In gem specs ~> is a Pessimistic Version Consrtaint that is inclusive on the bottom end. E.g., '~> 2.2' means '>= 2.2.0 and < 3.0'. I changed the translation to RPM spec to be >= and <. It was > and <. http://docs.rubygems.org/read/chapter/16 http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-advanced-packaging.html
This improves on the patch in #186. - Add tests to make sure exclude stays working :)
and chdir (-C) is set. Fixes issue #187 - Abort if there's no package name known.
bug/problem causing rpmbuild to use "/" as the BuildRoot on CentOS 5. Fixes #191. Confirmed working on CentOS 5.7 in a vm.
…hould fix #190)
(discovered by failing tests run on travis-ci.org)
digest/compress algorithms during package building. Defaults to the settings that are most likely to work on the widest range of rpm consumers (md5 + gzip) Improves solution already committed for #192
Fix attribute lookup for --deb-custom-control
… a sensible default of excluding nothing