Hi folks,
Thanks a lot for providing ruby193 packages for EL-6! I plan to use in combination with Jenkins in order to test Gitorious on this newer Ruby version.
Is there any chance of seeing ruby200 packages?
Also, with the "scl" tool, is there any way to avoid having to quote the additional commands? For example, it would be nice to be able to use the following line in a shell script in Jenkins:
$SCL bundle install
If the slave is using scl, then it would set the $SCL variable to whatever is needed. If the slave is just using the standard Ruby config, then $SCL could remain unset, and the bundle command would continue using the standard Ruby stack.
Currently scl doesn't allow me to run the "bundle install" without quotes. This means I have to branch the code like so:
if [[ -z "$SCL" ]]; then # No alternate Ruby version. Run as normal. bundle install bundle exec rake db:test:purge bundle exec rake db:setup bundle exec rake ci:setup:minitest test:units rcov else # Use the alternate Ruby version. $SCL "bundle install" $SCL "bundle exec rake db:test:purge" $SCL "bundle exec rake db:setup" $SCL "bundle exec rake ci:setup:minitest test:units rcov" fi
The large copy-and-paste has already bitten us a couple times, as the list of commands must be identical between both conditions. If I didn't have to use quotes here, I could just collapse it all down to the single version using
$SCL <command>
- Ken
Dne 6.7.2013 03:51, Ken Dreyer napsal(a):
Hi folks,
Thanks a lot for providing ruby193 packages for EL-6! I plan to use in combination with Jenkins in order to test Gitorious on this newer Ruby version.
Is there any chance of seeing ruby200 packages?
http://data-strzibny.rhcloud.com/ruby200srpms.tar.gz
Here are some Ruby200 SRPMs, but please note that this is just WIP
Also, with the "scl" tool, is there any way to avoid having to quote the additional commands? For example, it would be nice to be able to use the following line in a shell script in Jenkins:
$SCL bundle install
If the slave is using scl, then it would set the $SCL variable to whatever is needed. If the slave is just using the standard Ruby config, then $SCL could remain unset, and the bundle command would continue using the standard Ruby stack.
Currently scl doesn't allow me to run the "bundle install" without quotes. This means I have to branch the code like so:
if [[ -z "$SCL" ]]; then # No alternate Ruby version. Run as normal. bundle install bundle exec rake db:test:purge bundle exec rake db:setup bundle exec rake ci:setup:minitest test:units rcov else # Use the alternate Ruby version. $SCL "bundle install" $SCL "bundle exec rake db:test:purge" $SCL "bundle exec rake db:setup" $SCL "bundle exec rake ci:setup:minitest test:units rcov" fi
The large copy-and-paste has already bitten us a couple times, as the list of commands must be identical between both conditions. If I didn't have to use quotes here, I could just collapse it all down to the single version using
$SCL <command>
scl can read standard input, so you can do something as a:
$ scl enable ruby193 - <<EOF bundle install EOF
Not sure if that can helps you.
Vít
On Mon, Jul 8, 2013 at 1:28 AM, Vít Ondruch vondruch@redhat.com wrote:
scl can read standard input, so you can do something as a:
$ scl enable ruby193 - <<EOF bundle install EOF
Not sure if that can helps you.
Thank you. That works great!
SCL="scl enable ruby193"
$SCL - <<EOF ruby -v EOF
SCL="bash"
$SCL - <<EOF ruby -v EOF
and the output is:
ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux] ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
I have another question. Would you be open to upgrading the bundler package to 1.3.x ? The 1.1.4 version doesn't support Gemfiles with :ruby_20 platforms. Here's what happens:
$ bundle exec ruby `ruby_20` is not a valid platform. The available options are: [:ruby, :ruby_18, :ruby_19, :mri, :mri_18, :mri_19, :rbx, :jruby, :mswin, :mingw, :mingw_18, :mingw_19]
- Ken
Hi Ken,
Dne 11.7.2013 04:44, Ken Dreyer napsal(a):
On Mon, Jul 8, 2013 at 1:28 AM, Vít Ondruch vondruch@redhat.com wrote:
scl can read standard input, so you can do something as a:
$ scl enable ruby193 - <<EOF bundle install EOF
Not sure if that can helps you.
Thank you. That works great!
Great!
I have another question. Would you be open to upgrading the bundler package to 1.3.x ? The 1.1.4 version doesn't support Gemfiles with :ruby_20 platforms. Here's what happens:
$ bundle exec ruby `ruby_20` is not a valid platform. The available options are: [:ruby, :ruby_18, :ruby_19, :mri, :mri_18, :mri_19, :rbx, :jruby, :mswin, :mingw, :mingw_18, :mingw_19]
- Ken
If you could open RFE ticket in BZ, it would be cool. If you can open support ticket for RHSCL via RH's customer portal, it would be even better. It should be evaluated by PM, etc. I can't promise anything ATM. Sorry.
Vít
On Thu, Jul 11, 2013 at 3:22 AM, Vít Ondruch vondruch@redhat.com wrote:
If you could open RFE ticket in BZ, it would be cool. If you can open support ticket for RHSCL via RH's customer portal, it would be even better. It should be evaluated by PM, etc. I can't promise anything ATM. Sorry.
Sorry that it took me almost a month to get to this.
I had no idea that Red Hat's Customer Portal had a section for registering support requests for Software Collections. I guess I thought that SCLs were going to be more like EPEL. (In the long term, will there be any effort to make SCLs more like EPEL, and try to involve the community as packagers?)
This afternoon I filed a support request through work, and I'll let you know if the support engineer provides me with a ticket in Bugzilla.
- Ken
Dne 6.8.2013 01:44, Ken Dreyer napsal(a):
On Thu, Jul 11, 2013 at 3:22 AM, Vít Ondruch vondruch@redhat.com wrote:
If you could open RFE ticket in BZ, it would be cool. If you can open support ticket for RHSCL via RH's customer portal, it would be even better. It should be evaluated by PM, etc. I can't promise anything ATM. Sorry.
Sorry that it took me almost a month to get to this.
I had no idea that Red Hat's Customer Portal had a section for registering support requests for Software Collections. I guess I thought that SCLs were going to be more like EPEL. (In the long term, will there be any effort to make SCLs more like EPEL, and try to involve the community as packagers?)
This is official announcement of Red Hat Software Collections: http://www.redhat.com/about/news/archive/2013/6/red-hat-software-collections...
What is the future of SCL in Fedora/EPEL is unclear ATM. You are free to have SCL macros in .spec files and scl-utils are available in Fedora, but that is it. There is no other infractructure for SCL support in Fedora/EPEL (although Copr might help).
This afternoon I filed a support request through work, and I'll let you know if the support engineer provides me with a ticket in Bugzilla.
Great, thanks.
Vít
Dne 13.8.2013 12:15, Vít Ondruch napsal(a):
Dne 6.8.2013 01:44, Ken Dreyer napsal(a):
On Thu, Jul 11, 2013 at 3:22 AM, Vít Ondruch vondruch@redhat.com wrote:
If you could open RFE ticket in BZ, it would be cool. If you can open support ticket for RHSCL via RH's customer portal, it would be even better. It should be evaluated by PM, etc. I can't promise anything ATM. Sorry.
Sorry that it took me almost a month to get to this.
I had no idea that Red Hat's Customer Portal had a section for registering support requests for Software Collections. I guess I thought that SCLs were going to be more like EPEL. (In the long term, will there be any effort to make SCLs more like EPEL, and try to involve the community as packagers?)
This is official announcement of Red Hat Software Collections: http://www.redhat.com/about/news/archive/2013/6/red-hat-software-collections...
And this is additional documentation: https://access.redhat.com/site/documentation/Red_Hat_Software_Collections/
Vít
softwarecollections@lists.fedorahosted.org