You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Kirby C. Bohling" <kb...@birddog.com> on 2002/09/26 15:46:33 UTC
Read-only tags mentioned in the handbook
The handbook makes of using cp to create a tag, or a branch.
Specifically, it says that everything is a directory, and that the only
difference between a tag and a branch is the human applied
interpretation. It then mentions, marking tags as "read-only". I
searched for the "read-only" in the handbook and failed to see how you
could mark a tag that way. I'm guessing it's either a property, or an
apache config issue?
The specific sentence is:
"Each time /projectA/trunk reaches a taggable state, make a copy of the
directory somewhere in /projectA/tags/, and set the copy to read-only.
Use the same procedure to create a branch in /projectA/branches/"
Which is in the "Branches and Tags" section.
Did I miss it in the documentation? Sorry if this is obviously in the
docs, but I didn't see it mentioned anywhere else in the handbook. I'm
curious about how you do this.
The only other pertinate information I found is here:
"To restrict write-access only, you need to require a valid user for all
request methods except those that are read-only:
<LimitExcept GET PROPFIND OPTIONS REPORT>
Require valid-user
</LimitExcept>"
Would you just apply something like to to subdir's you plan on only
letting tags into? Just curious about how to actually enforce that a
tag can't be written to.
Thanks,
Kirby
--
Real Programmers view electronic multimedia files with a hex editor.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Tim Moloney <mo...@mrsl.com>.
Karl Fogel wrote:
> Kevin Pilch-Bisson <ke...@pilch-bisson.net> writes:
>
>>It could also be enforced by a pre-commit script couldn't it? I.e. any commit
>>to the tags/ dir, which was anything other than a copy to a new directory
>>would not be allowed to succeed.
>
> Yes! Don't know why we didn't think of that; it's the obvious easy
> solution.
>
> If someone who needs such functionality wants to write it (preferably
> as a Python module interface), we can put it in our tools/ tree...
I wrote a hook script and module in perl and posted it a while back.
Unfortunately, it no longer works (it probably wasn't that robust to
begin with) but someone smarter than me can probably figure out why
it isn't working any more.
Here's the old message.
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=164686
--
Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road \ /
Sarasota, FL 34232 .________\(O)/________.
(941) 377-6775 x208 ' ' O(.)O ' '
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Greg Stein <gs...@lyra.org>.
On Thu, Sep 26, 2002 at 01:40:37PM -0500, Karl Fogel wrote:
> Blair Zajac <bl...@orcaware.com> writes:
> > Geez, if it's written in Perl, it's not good enough, it goes unnoticed and is
> > quickly forgotten :)
>
> "Never attribute to malice what can adequately be explained by stupidity."
>
> It's not that it's in Perl, it's just that I'm forgetful :-).
I'm forgetful *and* I shun Perl :-)
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Blair Zajac <bl...@orcaware.com>.
Karl Fogel wrote:
>
> Blair Zajac <bl...@orcaware.com> writes:
> > Geez, if it's written in Perl, it's not good enough, it goes unnoticed and is
> > quickly forgotten :)
>
> "Never attribute to malice what can adequately be explained by stupidity."
>
> It's not that it's in Perl, it's just that I'm forgetful :-).
Thanks Karl. That wasn't directed to you personally, just a general
feeling on my part regarding Perl and Python.
Best,
Blair
--
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Blair Zajac <bl...@orcaware.com> writes:
> Geez, if it's written in Perl, it's not good enough, it goes unnoticed and is
> quickly forgotten :)
"Never attribute to malice what can adequately be explained by stupidity."
It's not that it's in Perl, it's just that I'm forgetful :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Blair Zajac <bl...@orcaware.com>.
Karl Fogel wrote:
>
> Kevin Pilch-Bisson <ke...@pilch-bisson.net> writes:
> > It could also be enforced by a pre-commit script couldn't it? I.e. any commit
> > to the tags/ dir, which was anything other than a copy to a new directory
> > would not be allowed to succeed.
>
> Yes! Don't know why we didn't think of that; it's the obvious easy
> solution.
>
> If someone who needs such functionality wants to write it (preferably
> as a Python module interface), we can put it in our tools/ tree...
Geez, if it's written in Perl, it's not good enough, it goes unnoticed and is
quickly forgotten :)
I wrote a pre-commit access control script and it's in the Subversion tree
already. See tools/hook-scripts/commit-access-control.pl and
tools/hook-scripts/commit-access-control.cfg.
I'm using it at the company I consult with.
Best,
Blair
--
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Kevin Pilch-Bisson <ke...@pilch-bisson.net> writes:
> It could also be enforced by a pre-commit script couldn't it? I.e. any commit
> to the tags/ dir, which was anything other than a copy to a new directory
> would not be allowed to succeed.
Yes! Don't know why we didn't think of that; it's the obvious easy
solution.
If someone who needs such functionality wants to write it (preferably
as a Python module interface), we can put it in our tools/ tree...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
Quoting Garrett Rooney <ro...@electricjellyfish.net>:
> Kirby C. Bohling wrote:
> > The handbook makes of using cp to create a tag, or a branch.
> > Specifically, it says that everything is a directory, and that the only
> > difference between a tag and a branch is the human applied
> > interpretation. It then mentions, marking tags as "read-only". I
> > searched for the "read-only" in the handbook and failed to see how you
> > could mark a tag that way. I'm guessing it's either a property, or an
> > apache config issue?
>
> the 'read-only-ness' of a tag is a purely social convention among the
> users of the repository. you could (i imagine) configure apache to
> enforce such a convention, but in general, subversion has not built in
> way to do so.
>
> -garrett
>
It could also be enforced by a pre-commit script couldn't it? I.e. any commit
to the tags/ dir, which was anything other than a copy to a new directory
would not be allowed to succeed.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson
kevin@pilch-bisson.net
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> the 'read-only-ness' of a tag is a purely social convention among the
> users of the repository. you could (i imagine) configure apache to
> enforce such a convention, but in general, subversion has not built in
> way to do so.
Yah, "read only" just meant "by putting the copy in /tags/, you're
telling people it shouldn't be written to". There's no technical
enforcement of the tags convention currently.
(Of course, we should implement directory tree access control in some
convenient way, i.e., a way other than reconfiguring and restarting
Apache; it's just not on the front burner at the moment.)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Read-only tags mentioned in the handbook
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Kirby C. Bohling wrote:
> The handbook makes of using cp to create a tag, or a branch.
> Specifically, it says that everything is a directory, and that the only
> difference between a tag and a branch is the human applied
> interpretation. It then mentions, marking tags as "read-only". I
> searched for the "read-only" in the handbook and failed to see how you
> could mark a tag that way. I'm guessing it's either a property, or an
> apache config issue?
the 'read-only-ness' of a tag is a purely social convention among the
users of the repository. you could (i imagine) configure apache to
enforce such a convention, but in general, subversion has not built in
way to do so.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org