Hi Patrick, * Patrick Ringl <[email protected]> [120618 17:48]: [..] > > > * ruby1.8: Now that ruby1.9.1 is the default ruby, it might not be a > > good idea to introduce a package that doesn't work on 1.9.x, > > especially when the executables say '/usr/bin/env ruby' (which > > likely will resolve to ruby1.9.1 on a standard installation). > > Upstream has a ticket[1] that 0.3.0 doesn't properly work on 1.9.x, > > and indeed you seem to have disabled builds for 1.9.1. > > Maybe it's better to package hiera 1.0.0rcX which is supposed to > > work on 1.9.x as well. > > > > I am fully aware of the 0.3.0 incompatibility with ruby 1.9.x (in > the original RFP which I split to two ITPs I mentioned this) - > therefor I disabled the 1.9.x build and used ruby1.8 as 'Depend'. > The 'shebang' is no problem, gem2ruby (or rather dh_ruby) will > cover this and rewrite the shebang properly (this is a lot cleaner > handling than using a patch imho, since it'll be done > automagically).
Right; I missed that because I temporarily modified it to build for all Rubies. > I am not sure if packaging the release-candidate makes more sense > - personally I'd really love to hear different opinions about it. > If we may find a common understanding (especially the one > sponsoring it) I can also package the release candidate in the > first place and thus (re)gain ruby1.9.x functionality (which > regarding wheezy makes absolutely sense). Well, could you do a quick check if the current RC will work with the puppet version in Debian? CC'ed mika who would upload your package. -ch -- christian hofstaedtler phone +43 720 699846 _______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
