I'm trying to solve the problem of developers committing code that was
compiled using stale externals. I was also trying to avoid requiring
pinning. Tags have to be pinned, and I have a script to check for that, but
not branches or trunk. I was hoping to reject the commit and have them
either pin the offending external or update to latest, at their choice (I
see the race condition, but our development is not that busy). So I'm
trying to be flexible. I like server side scripts because I can control
that, but I guess if it can't be done there I could have developers add a
client side script.
I'm guessing the answer is going to be to require externals to be pinned,
but that's a burden I was trying to avoid, particularly because clients
don't make it easy to manage them.
Thanks
On Mar 22, 2013 4:29 AM, "Daniel Shahaf" <d.s_at_daniel.shahaf.name> wrote:
Ryan Schmidt wrote on Fri, Mar 22, 2013 at 05:48:02 -0500:
>
> On Mar 21, 2013, at 18:27, luis montes wrote:
>
> > Is it possible to know the base revision on a svn: external from a
pre-commit hook script? If the external changes with the current
transaction I figured I could possibly parse the svnlook diff output, but
what if it does not change with the current transaction? I understand that
information is kept on the client, so does the client send it to the
server? For each external?
>
> I don't believe the client sends that information to the server.
Correct. The server is only concerned with the value of the
svn:externals property, the semantics of that property are oblivious
to the server.
Also, it's good practice to describe what you're trying to achieve at
a high-level, not only the particular solution you have in mind right
now. http://s.apache.org/xy-problem
Received on 2013-03-22 17:06:27 CET