Not the Xiphos repository, but the main CrossWire repository.
I generally use the Xiphos front-end app to install modules to my SWORD path
in Windows 7.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Module-upload-Bela-tp4657295p4657340.html
Sent from the SWORD
Your additional info seems to confirm that Xiphos accepted a typo in 2012,
and has not updated its listing since. The conversation should be how to
mitigate this (and similar typos that may also exist in other modules) in
the Xiphos repository.
On Sat, Jun 24, 2017 at 1:04 PM, David Haslam wrote
Peter knows that I was involved in some of the earlier activity on this
module.
It was I who established our initial communications with Dr. Alesya
Semukha-Greenberg.
Must be more complicated than that.
On 2014-11-28 I had archived Bela.zip which I just re-examined.
This was version 1.2 dated 20
Clearly, the problem was with version 1.0.5 being mistyped as 1.5
somewhere. a 'cleanup' version doesn't sound like a skip 4 type of
version.
On Sat, Jun 24, 2017 at 12:46 PM, David Haslam
wrote:
> I was incorrect in my earlier observation.
>
> Now I see why Bela didn't get listed under Updates
I was incorrect in my earlier observation.
Now I see why Bela didn't get listed under Updates in the Xiphos module
manager.
The newly available Bela version is 1.1
This surely must be incorrect because version 1.5 was released with
SwordVersionDate=2012-07-12
Why this backward step in version nu
On 06/17/2017 06:27 AM, David Haslam wrote:
> If *Bela* has "just" been updated, why doesn't it appear under Updates in
> the Xiphos module manager?
Someone probably just forgot update the version stamp. Presence in
Xiphos' mod.mgr updates depends on a simple comparison.
_
I'm confused!
If *Bela* has "just" been updated, why doesn't it appear under Updates in
the Xiphos module manager?
And yes - I know about Refresh...
The latest module is still version 1.5 - yet version 1.5 was released with
SwordVersionDate=2012-07-12.
Best regards,
David
--
View this me
