On Tue, Jul 08, 2008 at 02:15:42PM +0200, Mark Phalan wrote: > On Tue, 2008-07-08 at 14:12 +0200, Mark Phalan wrote: > > On Tue, 2008-07-08 at 08:00 -0400, James Carlson wrote: > > > Mark Phalan writes: > > > > > > > In our case we > > > > would like to have a single versioned script available for people to > > > > download and run on their systems for diagnostic purposes. No install, > > > > no package, no entry in any database anywhere. We can version the single > > > > file manually but we'd like to avoid that... > > > > > > If you're not part of the OS or packaging, then I don't see what > > > bearing this discussion has on you. You ought to be free to do > > > anything you want -- including choosing a source code management > > > system and build environment that supports whatever things you might > > > dream up doing. (And regardless of whether I or anyone else thinks of > > > those choices.) > > > > > > I'm confused. Why is this discussion about SCCS keywords, Mercurial, > > > and Solaris a problem for your project? > > > > The project (Kerberos) is hosted on opensolaris.org. We have a useful > > tool for people who want to diagnose problems with their Kerberos > > configuration. We are not (currently) planning on distributing that tool > > with (Open)Solaris. We are using the opensolaris.org infrastructure to > > host that script and would like a way to version it automatically. > > > > Perhaps it wasn't clear from the above but we'd like some way to do the > versioning without rolling our own infrastrucure/tools. Perhaps having > control of commit/push/pull hooks would be enough to implement this but > I understand that that is not possible with the existing setup.
Exactly. I was trying to follow the same methodology used by shell scripts that are part of ON when I added the krb-diag script to the OpenSolaris Kerberos repository and it wasn't clear to me how the version info was being handled. Given this is useful to the krb-diag script I asked the question. -- Will Fiveash
