On Tue, Feb 14, 2012 at 10:21:03AM -0500, Jason Guiditta wrote:
On 13/02/12 19:33 -0500, Wesley Hayutin wrote:
>
>I like your ideas, wanted to throw another out there..
>
>1. A scripted development environment.
>
>Why is it needed?? We have a complex application that pulls in resources from several
different sources.
>It would be cool IMHO if we had some certainty we're all looking at the same
thing. Should help with our collaboration, and with
>automated unit/cuke tests.
>
>Right now everything is very stable, but think back to a year ago when rubygem hell
rule the earth.
>It would also be cool if we didn't have to install the product first as well, but
not sure if that's possible.
>
>Thanks..
>
I have been thinking about something (I think) along similar lines. I
have some beginnings of this in conductor/util (build-all and a git
pull script that is not yet pushed), and martyn had a 'get all aeolus
repos' script in his own repo, maybe he can respond here with the link
again, so we have it together. My thought was to split out util into
its own repo, and have it contain developer tooling, possibly in the
form of a gem and optional rpm (that part highly tbd). A developer
wanting to work on the project would clone that single repo.
I think this would be great.
I also have a few rake tasks I've cobbled together that might make sense
there:
https://gist.github.com/1827545
== Idea 2 ==
We have been using rake tasks of 'rpms' and 'yum' for configure, -cli,
and -image. This code is currently duplicated in each project, which
drives me insane. I'd like to get this extracted _somewhere_, whether
it be some upstream project (which I think Mo mentioned a while back),
or just a gem/rpm to make the task available system-wide.
+1, it's been duplicated for at least 6 months and probably much more.