data_mapper gem assumes it is a gem
Reported by Jonathan Stott (namelessjon) | June 11th, 2010 @ 08:10 AM
The data_mapper gem requires rubygems, and also uses gem statements with explicit version pinning. I think both these things are bad. Even if we're not expecting people to require it, if we provide the file to be required, it should be well behaved.
Comments and changes to this ticket
-
Martin Gamsjaeger (snusnu) June 11th, 2010 @ 08:22 AM
- State changed from “unconfirmed” to “confirmed”
I agree, I see no reason why it's (still) done like that. Maybe it was kinda forgotten about?
-
Jonathan Stott (namelessjon) June 11th, 2010 @ 08:40 AM
Oh, yeah, I assume it was just forgetfulness. I'll write the simple patch :)
-
-
Jonathan Stott (namelessjon) June 12th, 2010 @ 08:16 AM
- State changed from “confirmed” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Jonathan Stott (namelessjon)
Martin Gamsjaeger (snusnu)
Piotr Solnica (solnic)