From: Jason Roelofs <jameskilton@...>
Date: 2006-12-05T00:24:09+09:00
Subject: Re: Wisdom of including Rakefile in releases

------=_Part_35252_15841204.1165245845797
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

rubyforge.org <-- All ruby / rails releases normally go here

sourceforge.net / freshmeat.net <-- everything else.

These places will give you a small space for a project-specific website as
well.

Jason

On 12/4/06, Trans <transfire@gmail.com> wrote:
>
>
> Hans Fugal wrote:
>
> > It's fully within the unix tradition of including the whole source in
> > release tarballs. It's true that unix 'make install' doesn't usually
> > install the makefile somewhere, though. I wouldn't worry about it, in
> > any case. If your rakefile is dangerous then you might want to rethink
> > it or put some sanity checks in. If you're worried about Joe Clueless
> > running a dangerous non-default rake target in some obscure directory...
>
> Good advice. I'll remove some of the default settings and mkdir_p's and
> raise errors in their place. Then not worry about it. Thanks.
>
> Slightly aside, where do others store their project websites?
>
> T.
>
>
>

------=_Part_35252_15841204.1165245845797--