IMHO: The approach is not *fundamentally* flawed. Perhaps it should be advisory at this time. But there are certainly some elements that are purely mechanical and these can be automated. And should be.
Cent from my fone so theer mite be tipos. ;) > On Dec 26, 2015, at 6:45 AM, David Haslam <dfh...@googlemail.com> wrote: > > Recent experience of how badly this works in practice has led me to the > conclusion that the approach is fundamentally flawed. > > When an experienced module developer submits a module for release, it is > unacceptable for his work to be altered by scripted changes to the conf > file. > > This reflects badly on the person who submitted the modules, and indirectly > damages their reputation. > > Given the complexities of the requirements set forth involved, I am of the > opinion that there is no subsititute for manual editing of conf files by > someone who is thorughly cognisant of these requirements. > > http://www.crosswire.org/wiki/DevTools:conf_Files > > > > David > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Submission-of-OSIS-files-for-Bibles-and-Commentaries-tp4655499p4655530.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
