FS#29130 - Split off ruby-rake

Attached to Project: Arch Linux
Opened by Silvio Knizek (killermoehre) - Tuesday, 27 March 2012, 09:39 GMT
Last edited by Thomas Dziedzic (tomd123) - Friday, 30 March 2012, 15:14 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Wish:
Please move ruby-rake out of ruby, so it can be an explicit dependency (usefull for gem2-arch-ruby).
Thank you.
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Friday, 30 March 2012, 15:14 GMT
Reason for closing:  Won't implement
Additional comments about closing:  see last comment for explanation
Comment by Dave Reisner (falconindy) - Tuesday, 27 March 2012, 13:17 GMT
What's wrong with the current setup? gem2arch-ruby is a ruby script. It requires ruby already, so rake is included... What's the benefit of breaking out this single binary? Why would we break out rake, and not irb, or gem?
Comment by Thomas Dziedzic (tomd123) - Tuesday, 27 March 2012, 13:33 GMT
This will create cyclic dependencies since you expect ruby to include rake (since upstream ships it with ruby by default) and rake is going to expect ruby.
Same with splitting out gem and irb.

ruby also has:
provides=('rubygems' 'rake')
conflicts=('rake')

If you want to use explicit depends, then depend on rake which ruby provides.

Loading...