RE: implementing basic metadata in cvs using tags

2001-10-16 Thread Matthew Herrmann
--- Far Edge Technology tel: +612 9955 3640 11/80 Mount St North Sydney NSW 2060 Australia -Original Message- From: Paul Sander [mailto:[EMAIL PROTECTED]] Sent: Sunday, 14 October 2001 19:09 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: implementing basic metadata in cvs using

RE: implementing basic metadata in cvs using tags

2001-10-16 Thread Paul Sander
In that case, take a look at the -o and -u options that can be used in the modules database. These features are pretty gunky but they might fill the bill by allowing you to register programs to execute during checkout and update. The downside is that they drop cookies in your sandbox that can't

RE: implementing basic metadata in cvs using tags

2001-10-16 Thread Greg A. Woods
[ On Tuesday, October 16, 2001 at 18:28:52 (+1000), Matthew Herrmann wrote: ] Subject: RE: implementing basic metadata in cvs using tags Arguably it _is_ for a build system to register libraries etc., but as I work in interpreted languages where the compilation is usually incremental (check

Re: implementing basic metadata in cvs using tags

2001-10-14 Thread Paul Sander
Do you really believe that overloading symbolic tags is a good idea? What value do you set the special tags to? Are users allowed to modify them with the usual tag commands? Do you want users to see them with the usual log commands? Do you want to prevent users from using them as version

Re: implementing basic metadata in cvs using tags

2001-10-14 Thread Greg A. Woods
[ On Sunday, October 14, 2001 at 16:09:36 (+1000), Matthew Herrmann wrote: ] Subject: implementing basic metadata in cvs using tags why not have registered programs on the client side which mangle permissions and so on into a sort of UUencoded string, put into a file's tag, which is then