On 11/15/06, Ryan Schmidt <email@example.com> wrote:
> On Nov 14, 2006, at 09:21, Timothy Madden wrote:
> > 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 ?
> To the best of my knowledge, Subversion doesn't support that, and I
> don't think there are any plans to do so. My recommendation would be
> to separate the data in your repository so that everything you want
> to publish to the web server is located in one directory (in my
> projects I call this "web"), and everything you use during
> development but which should not be on the live server in another
> directory (I call this "dev"). Then check out (or export) only the
> "web" directory on the web server.
> > 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 ?
> Subversion does not support relative or absolute paths in externals;
> it only supports complete URLs. See this open feature request, which
> I found by searching the issue tracker for "externals":
Separating project files into web and dev directories is not always
practical. There are tools that assume support files stay the same
place as source files and will need more configuration work if you
want things otherwise (if at all possible).
I would rather write a shell script that checks the class property for
every file and dir created by svn-export. But I think Subversion is
better able to do this.
As for the externals thank you for the link on the issue tracker. I
posted my ideea on issue 1336, I'll wait to see if anybody answers.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 15 12:33:31 2006