Re: [trinity-devel] lsm files

I am willing to do the grunt work to update these files. Yet after updating various branding issues, a remaining challenge is with each release the files all need updating again. Anything like that is best suited for the computer with scripts. Two fields should be updated with each release: Version Entered-date Both fields should be updated to the release version/date. I prefer to see something built into the build process, such that even GIT builds reflect correct information. Another challenge is whether these files are still maintained and whether we should resubmit our updated files to the lsm database. Tim, What is a good way to automate this? Comments? Darrell