From: Trans <transfire@...>
Date: 2008-07-03T10:33:09+09:00
Subject: Re: Worthwhile to build a gem?



On Jul 2, 6:59 pm, Greg Willits <li...@gregwillits.ws> wrote:
> Trans wrote:
> > On Jul 2, 5:14pm, Greg Willits wrote:
> >> I have a project where a number of internally-developed Ruby libraries
> >> will need to be installed on numerous machines. Small apps will then be
> >> written using this set of libraries almost like a framework really.
>
> > Will these libraries all be in single project (ie. gem), or do your
> > see them each as separate projects?
>
> The libraries form a single core of tools and logic upon which to build
> server side data aggregation apps.

Cool. I'd say create a gem for it. Would Capistrano be helpful?

> >> Is it worth considering building a gem out of this library and running a
> >> private gem server in order to manage these libraries? The alternative
> >> would be to maintain working copies (maybe in site_ruby?) from an svn
> >> server -- much like you'd typically maintain a Rails app on servers.
>
> > your [you're] using svn rather than git I take it.
>
> svn, yes. If I changed my code with every new fasionable thing, I'd
> never get anything done. svn works just fine for me.

:) i can relate.

T.