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

RE: pre-checkout/export hook

From: Eric Clark <eclark_at_ara.com>
Date: 2005-10-19 21:19:28 CEST

Hey Guys,

I was not intending for this question to start any bad responses between
developers, but I do appreciate everyone's response. Let me explain my
situation in a little more detail:

Thank you for re-iterating the svnserve thing because I had missed that. I
am not in extreme hurry to get this implemented, but I would like to see
something as soon as possible. I looked into the svnserve thing and that
could be a possibility for me. I will look into using it when 1.3 is
released; however, I would still like to know if anyone is planning on
implementing hooks for pre-checkout/pre-export, I believe that this would be
a good feature to add to subversion as you have hooks for many other things
already, and adding a pre-checkout hook should not be too difficult. If I
was a Subversion contributor, I would do it myself, but I do not have the
time and I apologize for that.

Yes, moving the sensitive stuff to separate repositories is probably the
only solution that will work for me right now, and that is the best
suggestion I've heard thus far for what I can do right now, thank you.

I have read the dev list and I do see that 1.3 RC1 is due out any day now;
however, I do not like working with release candidates and I would prefer to
wait until there is a stable 1.3 out. When the stable version is out I will
try to use svnserve to do what I need. However, I still believe that a
pre-checkout hook would be very useful. I am not the only one that has
requested this (if you read the mailing list archive or google pre-checkout
for subversion). There are many people out there with this same problem and
that should be enough to get someone to implement it, especially since it
would not be a difficult feature to add. If I knew Subversion's code and I
had time to work on it, I would do it myself, but I don't, and that is why I
am sending this message out to the developers. As for not using Apache, this
is a Government policy, not a company policy, and if you would like to
evangelize the government go for it! The code that is in our repository is
government owned and very proprietary. So, using Apache is out of the
question for two reasons (and very important ones at that): the government
will not allow an http server to reside on this machine, and when checking
in and out of the repository, the code needs to be encrypted. Since http
does not encrypt the data, Apache is again out of the question.

Again, thank you everyone for your responses. I am still looking for an
answer to whether or not anyone plans on implementing the pre-checkout hook.

Thank you,

Gale, David wrote:
> Eric is looking for a solution for _now_, today, not some point in the
> future when 1.3 is released. Marcus's answer (authz through apache, or
> wait for 1.3) didn't fulfill his needs, so he asked for anyone who had a
> more immediate solution; your response was to simply parrot back the
> answer that he'd already received, and determined to be inadequate!
> This would be acceptable if he'd simply missed something in Marcus's
> reply, and you were drawing his attention to the pertinent information;
> however, that's simply not the case.

Except that I responded specifically because it appeared that Eric had
missed the mention of svnserve (since he only discussed why Apache
wouldn't work), or didn't realize it covered his case (which is why I
went into more detail than Marcus did). I also got no impression that
Eric needed something /now/, as opposed to /later/, merely that he
believed that the only way he could accomplish his task was via
pre-checkout/pre-export hooks. His original e-mail was merely querying
as to whether "there are plans on implementing these hooks" not that he
had to have it now.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-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 Wed Oct 19 21:20:16 2005

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

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