As far as I know, with IN SVN, NO. However, my PERSONAL assumption is
that a tag is ALWAYS read only. :) IE we here all KNOW, when someone
creates a tag, do not EVER EVER copy anything else into the tag. (IE I
JUST created a new tag called release for a release of a piece of
software. For all eternity, you will always be able to refer to it as
/Tag/release and get the code that we sent out the door at Version 1.0.
:))
A feature that I want to add on top of SVN at SOME point is some kind of
automated content management/delivery system. haven't thought it all
out yet but something like this:
We all are working on a web site. I commit a change to a PHP script.
It then at a specific time (or when I TELL it to) goes and updates our
staging server code. Everyone then goes and tests it and says "Yes it
is GOOD.". I then run ANOTHER command that goes and either Exports or
just does a copy or something (IE this part I've not REALLY figured out
at all. LOL) over to the live server.
There could also be a web page for non programmers to upload changed/new
files into the staging server and then let em check it in.
And since I can ALWAYS access the repository via http... :) it works
well for us since we're all remote users.
And ya know.. I JUST had a thought!!!
YOU MIGHT be able to make a portion of the repository read only via
APACHE!!!
IE something like this:
<Location /Tags/release>
<LimitExcept GET PROPFIND OPTIONS REPORT>
deny from all
</LimitExcept>
</Location>
This would make it read only for EVERYONE. OR!!!!
<Location /Tags>
<LimitExcept GET PROPFIND OPTIONS REPORT>
require user tag-manager
</LimitExcept>
</Location>
This would make the repository read only to everyone but the tag-manager
user. Control who has that password and you're in business.
Note: this will NOT work for accessing the repository via the local file
system.
The more I play with SVN, the more AMAZED I am at it's potential!
Whoever decided to use WebDAV and Apache is a GENIUS! :)
On Thu, 2002-10-10 at 03:46, Morten Ludvigsen wrote:
> --- Jeff Stuart <furball@weboverdrive.com> wrote:
> > If you're going where I THINK you're going with this. :) (IE automated
> > rev control of web pages) Instead of relying on a SPECIFIC rev in the
>
> Something like that :-) The idea is to have information about which revisions
> of which files should be accessible, and when they should be accessible.
> Using that information a system that sits on top of subversion can serve
> the correct revision based on the current time.
>
> > repository (Don't forget, rev numbers are NOT per file but basically per
> > check in.) Instead create a tag and use THAT to always
> > checkout/access. So you're URL is just
> > http://repos.domain.com/tag/<your tag>/<filename>. That way, you're NOT
> > dependent on a feature that the developers say WILL change, instead,
> > you're using a feature that is already a part of SVN and won't
> > (HOPEFULLY!) ever change.
>
> Thanks for the suggestion. I think this is the way I will be going, as I have
> dropped the other idea. The really nice thing about using revision numbers would
> have been that I would know that the file in the requested revision would never ever
> change. This is important for caching reasons. This brings me to my next question:
> is there a way to mark a directory (tag) read-only?
>
> Regards,
>
> Morten Ludvigsen
> 2-People Software
> Denmark
>
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 10 10:15:48 2002