[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Features request - advanced behaviour for export and working copies

From: Timothy Madden <terminatorul_at_gmail.com>
Date: 2006-11-14 16:21:10 CET

Hello

In many projects, like web sites, the files under version control can
be divided in two groups: public files that are ment to be published
on the web server, and other script files that are usefull to
configure my editor and development tools, and for custom commands.
And maybe there can be other kinds of files in a project.

When I have a new release ready for my site I would like to use svn
export to get a fresh copy of the sources and publish them. For
security reasons I would never publish more files than necessary and I
want 'svn export' to retrieve only my public files (because I also
have other files under version control meant mainly for development).

This is why I would like to create some 'class' or 'svn:class'
property and set it on each or most of my files, and I would like svn
export to understand some options so that it will only export files
with a given value in the 'class' property (or in any other properties
I need) or only export files that are missing a given value from their
'class' property.

Do you think it is possible to implement this in Subversion ?

Or better yet, I would like svn to directly manage my public folder,
so I could just update instead of export the entire site. But I would
like no administrative files in my public folder, just the source
files. Do you think it is possible to implement release copies (as
opposed to working copies) in Subversion ? These copies would have
their administrative files automaticaly placed somewhere else.
%APPDATA%\Subversion\release_copies on Windows platforms would be
good. Or it could be that Subversion allways requieres an argument
with the path to the administrative area in order to so any work with
such release copies.

Do you thnk this could also be implemented in Subversion ?

And will the svn:externals behaviour be fixed so that svn supports
relative path names for the externals in a repository ? The book says
svn:externals has as a disadvantage the missing support for relative
paths, but are relative paths going to be supported ?

Thank you
Timothy Madden
Romania

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 14 16:22:22 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.