|Sent on:||Thursday, November 3, 2011 5:54 PM|
On Thursday, November 3, 2011 at 4:07 PM, George Mauer wrote:
Hey guys, I have a question about the workflow of a gem author.Suppose I have a project "MainProject" and while working in it, I realize that a bit of code would be useful for others to distribute as a gem.So I extract that code, minimize my dependencies, commit it to its own github repository, and package it as a my-awesome-gem gem. Great.Now I have two choices as far as I can tell.1) I can remove the code entirely from MainProject and re-include the gem. Then, if in the course of development on MainProject I fix a bug in my-awesome-gem I would fix it in the my-awesome-gem repository, recreate the gem, and update it in MainProject.or2) I can leave the code in MainProject and fix it as I work, after making changes I would copy/paste the changed files into the my-awesome-gem repository and push that out.Neither one of these is appealing. Is there a third option? What do you guys do?
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by George Mauer ([address removed]) from Ruby Bayou.
To learn more about George Mauer, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]