[sword-devel] MinimumVersion property in module.conf files
chrislit at crosswire.org
Tue Aug 6 07:42:09 MST 2013
Often, there's some obvious feature that requires a minimum Sword
version. Absent that, I have been setting 1.5.8. I'll probably bump that
to 1.6.1 after the release of 1.7.0.
There are two functions of MinimumVersion. One is to shelter users from
modules they can't use. Another is to strongly encourage users to
upgrade, nag their front end's maintainers to update, or switch to a
better-maintained front end-- we don't need to be dealing with library
bugs that were fixed five years ago.
On 8/6/2013 12:48 AM, David Haslam wrote:
> (I hope these don't seem too naive to be asked in erudite company!)
> When it's not something obvious such as support for av11n, how does one
> determine what to specify for the *MinimumVersion* property in module.conf
> Example: Suppose I make a module using osis2mod from version 1.7.0 RC2 or
> later, must I set
> or is the answer/explanation much more complicated?
> Is this informatic property purely related to module installation, etc?
> Or is it something that front-ends might take into account?
> View this message in context: http://sword-dev.350566.n4.nabble.com/MinimumVersion-property-in-module-conf-files-tp4652983.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel