Hi guys,
Anybody have any experience with some scripts for bash completion? Have
you tried any? Should we integrate any? Just a quick googling gave me
two results:
https://github.com/mernen/completion-rubyhttps://github.com/pdkl95/rubygems-completion
And there are probably others. I did not tried them yet. Have you? Do
you have other/better tips?
Thank you
Vit
I know that both result to the same thing (if I remember correctly I had
asked Vit about this in IRC), but I have forgotten their real difference.
My attention got caught by a comment Josef made in one of his reviews
[0], saying that rubygem-foo is the new syntax. If that's the case, I
would like to propose 2 changes:
a) A reference in the wiki
b) An implementation for gem2rpm
I guess b) could be fairly easy by changing the templates.
By starting with these steps, there will be a push to use the new syntax
from now on. What do you think?
[0]: https://bugzilla.redhat.com/show_bug.cgi?id=979749#c2
--
FAS : axilleas
GPG : 0xABF99BE5
Blog: http://axilleas.me
Hi rubyists,
Working toward Ruby 2.1.0 in Fedora, there are going to be necessary
some changes to gems with binary extensions. In short, the extensions
are not installed into %{buildroot}%{gem_extdir_mri}/REQUIRE_PATHS/
anymore, but %{buildroot}%{gem_extdir_mri}/ will be used for the future.
This is improvement and this change is coming from RubyGems upstream. It
should also simplify the guidelines a bit [1] (on the first look).
Unfortunately, although the resulting rubygem- packages are much nicer
and closer to upstream then they used to be, the way how to create them
got uglier :/ You can see changes needed to make rubygem-bcrypt-ruby
compatible with new RubyGems in attached diff.
Since I am not happy about the situation, I'd like to ask you for your
feedback, how would you envision to simplify this process.
I am thinking about several possibilities:
1) Modify our operating_system.rb and let it treat gem installation into
%{buildroot} specially
2) Use some environment variable, to let RubyGems know, that we need to
treat %{buildroot} similarly to system directories
3) Introduce some additional parameter to gem install command, which
will modify the --install-dir option to install extensions properly
4) Introduce some RPM macros which will handle all this stuff for us.
Please let me know if you have another bright idea :)
Thanks
Vít
[1] https://fedoraproject.org/wiki/Packaging:Ruby#Building_gems
Hi rubyists,
I put together change proposal for Ruby 2.1 in Fedora 21 [1]. Any
feedback is welcome. If no feedback, I'll propose this change to package
wrangler in a week or so ...
Vít
[1] https://fedoraproject.org/wiki/Changes/Ruby_2.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey,
Anyone willing to review or swap reviews? I still need to be
sponsored, since I don't have a package in Fedora yet, but I'm happy
to do an “unofficial” review.
https://bugzilla.redhat.com/show_bug.cgi?id=1052524
Henrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJS1F4MAAoJEBSXlMsKCt+/UBEQAImVewn//k3hlxlCTHCaLFb/
EHIwClh+nPoxWjl7nY/QjUPcRact198RzhKBChiLyQGQiMj6r1ts8KMhXU6wtGcM
sBPLADuspLumXXLb8BDJHy1WPNyNwj7cxeP9sO/K+NS5amTyi/Nhku3lIJg79xAG
wfgoeiT/Asrgf+udOre9012Eq0ORhrUtlCeYdSv75iKeydIU6QJbB2ys3Ra+6hKV
m0ilyjQbWH7nDrVcmZwDlYoZDyR7q3J27uvCXTDkEyzTpV+fG32/yfGT8E2SFG6e
Q83gmwvt0Tp/KdU/5YgIad93VNv3WADIGLl25ppsD4k+Qyy9I6AwqwwvEa+rTdMA
fXDUVpDjI0y9pTjhXNZ6fHcHc59ywIeLMoZ9tuOYDB2bVZPpkShX4s85qV16P0ry
Q6oIRlSLAkTjcN08YH1utPyO7AKdSiLPej07pTLuPrMAHa+eTEGasJKwzU/Qr29f
f5gl8xID1HBYd+SqYZkc96DKjFXbFnZ2KeS0yCoD7KCoNTJ8/Yz4+UQV6FRdd2rz
wnbOT2IYiVkngSqkrJaX7n3RgU5cvTq/SMslpf7TJmzivnQb9qkOcn0lz6T2LZ6d
ySB/G13WL9/U5rsE5cVhoCGZuIpNl7FAQ//QdJ+5HVUdx3o1jvE5ca0cm3/wnfT7
fpMSGYh1T8jsqpZaAFCw
=Ijxs
-----END PGP SIGNATURE-----