Re: Subversion, gem packaging, externals, and symlinks

Joe Van Dyk
2005-07-13T06:00:44Z

On 7/12/05, Michael Schuerig
<michael-q5aiKMLteq4b1SvskN2V4Q@public.gmane.org>
wrote:
>
> I''m scratching my head over how to make subversion do what I want.
> During development I track the SVN HEAD release of Rails linked-in as
> an external in the vendor directory. For the Rails-related files in the
> public directory I use symlinks to the original files.
>
> For development this works, but not for tagging and building a release
> gem. The problems I''m currently having are these
>
> - When tagging the current version by svn copy-ing it
> to .../tags/release-0.x.0, the release of the svn:external for Rails
> still points to SVN HEAD, not to the revision current at the time of
> tagging. I don''t see how to fix the Rails revision without
error-prone
> manual intervention.
>
> - The relative symlinks break when rake gempackage copies files to its
> working version that it uses for packaging. I think that symlinks to
> external files, i.e. ones not included in the package, should be
> substituted by the original files. That would require changes to gem,
> though. Is it possible to get the same result without them?

I''d like to see an answer to this too!  I can''t figure it out
either.

Also, why do you use gems to package a rails site?  What''s the benefit?