
Updates for Rakefiles in dm-more that fix "rake install"
Reported by Joey B | April 11th, 2008 @ 06:32 PM
My commit details should tell the story:
Updated Rakefiles so that a rake install will succeed.
Changes included updating directory names, omitting package files that do not exist and omitting dm-serializer because it does not have a Rakefile (so it cannot be installed via a rake install at this time).
One potentially controversial change is that I removed the install step where dm-more attempts to install dm-core. When I started working on the file it was trying to install dm straight up. No such gem. And since dm-more is dependent upon dm-core, I didn't see why it would try to install dm-core at all ... make sense? I think so.
This commit is available for pulling from:
git://github.com/joe/dm-more.git
And is represented by commit:
cb0efe5394a7ed
Comments and changes to this ticket
-
Joey B April 12th, 2008 @ 11:32 AM
I just noticed that guyvdb on github checked in a Rakefile for dm-serializer, so (as long as the Rakefile is functional) my commit will unnecessarily remove dm-serializer from the parent gem's install task.
I'm making more commits to my fork today related to rake and gems and merb integration ... and bringing dm-serializer back into the mix along my commit line is one of the things I'll commit.
-
Dan Kubb (dkubb) April 14th, 2008 @ 05:19 PM
- Milestone cleared.
- State changed from new to open
-
Sam Smoot April 27th, 2008 @ 10:50 PM
- State changed from open to resolved
I think we've got this settled. Feel free to reopen Joe if I missed something.
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 your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »