* Mark Phalan <[EMAIL PROTECTED]> [2008-07-08 07:42]:
> On Mon, 2008-07-07 at 16:53 -0700, Stephen Hahn wrote:
> > * Mark Phalan <[EMAIL PROTECTED]> [2008-07-07 12:32]:
> > > Is there any way for us (as repository admins) to have scripts run when
> > > a push/pull/clone is performed - i.e. hooks on hg events?
> > 
> >   Not on an opensolaris.org server.  You could run a clone that uses
> >   your specific hooks, and run updates on a periodic basis. 
> > 
> >   If you have specific ideas about what you want to do in the scripts,
> >   it's probably best to describe them--they might be of interest to
> >   other projects.  In that case, we might be able to generalize them and
> >   add them as an option to the current hooks.
> 
> The main reason we'd like to have the ability to run hooks is due to the
> lack of a way to do automatic versioning. Under SCCS control the script
> can use SCCS keywords but hg doesn't have the same concept. This topic
> is being discussed on tools-discuss but the general feeling there seems
> to be that SCCS keywords are generally evil and that some other form of
> explicit versioning should be used. As this script is a standalone
> diagnostic script we don't want to package it and would like to avoid
> manually bumping the revision number every time we do a push.

  Well, the tools-discuss gang would own to hooks, so I doubt that's
  going to work.  You might consider moving your auto-versioning to
  publication time (make install) rather than integration time, and
  distribute your published version, rather than a copy from your source
  repository--that is, deliver the build *product* and not the source
  code.  (Yes, I read that it's a script.)

  - Stephen

-- 
[EMAIL PROTECTED]  http://blogs.sun.com/sch/
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to