Message: previous - next
Month: May 2012

Re: [trinity-devel] lsm files

From: Darrell Anderson <humanreadable@...>
Date: Fri, 25 May 2012 17:05:58 -0700 (PDT)
> > What is a good way to automate this? Comments?
> >
> One way to automate this would be to have a script that is
> run just before each release that finds/replaces placeholder strings in each
> lsm file with the current information.

Is this something we can automate as part of the automake/cmake build process? Or is this something we relegate to the etherpad release check list?

> Of more concern is the fact that many of the lsm files are
> completely out
> of date or just plain wrong, referencing KDE in many cases.

Yes, that is how I got started on this. I am about to embark on another branding cleanup exercise. Yet there is a method to the lsm madness and we should not blindly search and replace. There are fields for recognizing the original authors, for example, and they should be retained or updated as necessary.

I found 104 lsm files in the GIT source tree. Not bad, and many are part of the same module, which means only one patch each.