Re: Sharing files

>> Sorry to come back with the question but is there any known workaround
>> that I could use to link directly to a file instead of the whole
>> directory ?
>> Also, is there any plan to address the file sharing limitation in future
>> release of svn?
>
>This is at least the second time this issue comes up today! See
>"svn:externals should work with files as well as directories" at
>http://subversion.tigris.org/issues/show_bug.cgi?id=937

This is one of the bigger limitations for me.

I have a library of thousands of routines. Each is in its own file.

When I write projects for cliients, I want to include *only* the library
routines that project uses. I certainly don't want to give the client my
entire library, and I really don't want to give them 500 string-parsing
functions (or whatever) when their project only uses 3 of them.
(this is also why each routine is in a separate file, btw - so I don't give them
a single file that contains an additional 497 useful routines that they haven't
"paid for")

Putting all the thousands of individual files in subdirectories (so I can
individually svn:externals them at a directory-level right now) would be absurd.

Ideally, any changes to the library files (in a working copy) would be checked
back in to the repository, of course, but I'd be fine without even that - just
give me a way to do a checkout and populate the project's library directory with
individual files.

I'd rather have something that works for _some_ cases *now* than wait for it to
work for _all_ cases years from now. (i.e., if it doesn't handle checking back
in, fine. if it doesn't handle permissions, fine, if it doesn't handle
whatever, fine...)

- Al -

-- 
--  Alan Weiner  --  alan_at_ajw.com  --  http://www.ajw.com
Palm OS Certified Developer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org