Slowly upgrading all fubu projects to Rake 10.0.3

[Jeremy D. Miller]

Folks,

I honestly don't know how much trouble this is going to cause, but I've been slowly bumping up the fubu-related solutions to using rake version 10.0.3 as I get the "oh dear, you're trying to use the wrong version of rake, try bundle exec rake…" message.

At some point, we need to figure out how to make the builds much easier to use for newbies. The biggest problem is still ripple/nuget, but Josh is on that one. That still leaves us with the InstallGems.bat, rake, bundler confusion. If it's a better set of README's or a simple "BuildMe.cmd" in the root that manages both the bundler call and then rake, that's great.


Any ideas?

Jeremy

[Corey Kaylor]

That sounds fine to me. I've been tempted to try out Fake (F# make), to see if it might help. fsx files are executable scripts and wouldn't require any installs. Big fix for a little problem IMO though.

Jeremy

--
You received this message because you are subscribed to the Google Groups "FubuMVC Development Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fubumvc-deve...@googlegroups.com.
To post to this group, send email to fubumv...@googlegroups.com.
Visit this group at http://groups.google.com/group/fubumvc-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Matt S.]

I like the idea of a build batch. However, something in that file, and/or the readme, just mentioning some of the build tech being used would be great too. Some people will just want to build and get through their contribution. However, I had only subconsciously heard of Rake before my first contribution. Having to dig a little bit, for me, turned me on to Rake as a tool that I now use for all my new projects (and some old project builds that made me want to kill a unicorn).

So, for those that want to dig around a little, they could very well learn about something not directly related to Fubu that opens up a whole new world. Not only that, but nobody wants to see a dead unicorn.

-Matt

[Peter Wetzel]

+1 to that; it doesn't have to be extensive, simple descriptions and maybe a link to a home page (if applicable). Going into a new project can be like learning a new language; defining commonly used technology/terminology would help new folks get up to speed. Like most documentation things we should have, I think it exists already, just scattered around on numerous related sites, blogs, etc. Or it's embedded within Jeremy/Josh's shared brain.