How to track a file (in various versions) used by several projects

[Steve Mullock]

Dear Norman

Thanks for clarifying. I think I understand now.

In the heat of the moment I don't entirely trust myself to always remember to edit a MODIFIED
line. Also in the library repository, it would be useful to have some history that tells me 
where changes came from. So I think I pursue the named branches route for a bit, in the hope 
Mercurial will help keep track of things for me. After a few drift apart and merge events, I 
should have a clearer idea how this will work out.

Thanks again

Steve

From:           	Norman Gray <gray at nxg.name>
Date sent:      	Thu, 19 Oct 2023 17:18:42 +0100

> 
> Ah, no, I wasn't thinking about compiled code.  The specific case here is a local, but quite
> intricate, LaTeX class file, and some associated other files (images, and XSLT scripts).  Once
> they're in place in the 'client' repo, they're included from there by LaTeX documents in that repo.
> 
> Thus the client repo remains standalone, but I have a mechanism for bugs which emerge in the class
> file, to be fixed in one client tree, and then be coped back to the 'library' repo, where they can
> be bundled into a 'distribution' (strictly in scare-quotes), ready to be copied into other
> 'clients', when that becomes convenient.
> 
> There's a few by-hand steps in the workflow (if feels dodgy even dignifying it with 'workflow'!),
> and there might be a way which uses more Mercurial cleverness, but the process is fundamentally
> simple enough that this works for me.
> 
> Best wishes,
> 
> Norman
> 
> 
> -- 
> Norman Gray  :  https://nxg.me.uk

-- 
Dr. S.J. Mullock 
http://www.kore.co.uk
Kore Technology Ltd
Cambridgeshire Business Park
Ely, Cambs.
CB7 4EA, UK
Tel. (Int.+ 44) (0) 1353 653030
Fax. (Int.+ 44) (0) 1353 653031
Registered in England, No. 2643175