> -----Original Message-----
> From: Wayne [mailto:wayne_at_zk.com]
> Sent: Wednesday, 13 February 2008 14:42
> To: John Niven
> Cc: Ethan Schlenker; users_at_subversion.tigris.org
> Subject: Re: Adding a file to repos with a post commit hook?
>
> > I don't see why not (though I've limited experience with post-commit
> > hooks). I can think of two possible approaches (disclaimer: I'm out
of
> > my SVN comfort-zone now, my experience with hook scripts is really
> > limited to ensuring there's a log message, but it is something I've
been
> > looking into recently):
> >
> > 1. If all your developers are using TortoiseSVN you could create a
> > client-side hook that regenerated the compressed js file(s), then
> > committed the new file(s). This relies on all your team using
> > TortoiseSVN (and, by extension, Windows);
> > 2. Have a working copy on the SVN server, and a server-side hook to
> > regenerate the compressed file using new uncompressed file. This is
> > almost certainly the preferred option.
> >
> > Hope this helps, and sorry I can't be more helpful
> > Cheers
> > John
> >
> >
> To me this method seems problematic. Developers are going to commit
> there changes and then forget to update there working copy. Then
they'll
> waste time trying to figure out why the new code they added doesn't
fix
> the problem only to find out it did but they are testing the old
version
> of the compressed files.
> I don't work with js but it would seem to me that you'd want something
> in place that make sure that the compressed version really matches the
> version the developer is looking at.
Agreed, that's why I'd be reluctant to store anything other than source
in SVN. I still feel something like compressed javascript falls into
the "binary" category, i.e. it's rightfully a product of the build
process, and should only be generated when needed, i.e. before
deployment to a test server, etc. I think *any* solution to this is
going to involve some problems at some point; it boils down to what the
original poster is comfortable with - and getting the developers to
update regularly may be easier than convincing the powers-that-be that
the development process may need revising ;-)
Cheers
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-13 03:04:29 CET