Hi, Peter Michaux wrote: > On 9/6/06, John Clayton <[EMAIL PROTECTED]> wrote: [...] >> Anyway, just from a practical standpoint, I'd still like to find a >> non-subversion way to capture official releases. Might be as simple >> as requesting they be posted as tarballs ... > > I think it is practical to have SVN installed on your computer if you > are in the Rails world. That way you can do this stuff without > spending any time worrying about it. Just "svn export" and you are > finished. Is there some sort of security problem you are worried about > by having and SVN client on your computer?
I don't know of any other language that has a SCM system as a dependency. For configuration management purposes, you really need a way of tracking what revision is installed where - pulling untagged releases from SVN/CVS/whatever is a really bad idea in some environments. Tarballs have the advantage of being a single, unchanging entity that can be cryptographically signed, checksummed, etc. to assure the end user they know what they're downloading, plus they can easily be stored on tape, CD, whatever for disaster recovery purposes. I'm playing devil's (or John's) advocate here; while I like the option of retrieving code via SVN, it still feels risky, like I'm using bleeding-edge code rather than something tested and approved for release even if that's not the case. I'm leery of using SVN as the primary or sole release mechanism. YMMV, -- Bob _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
