[sword-devel] merge raw & avraw repos?

[Chris Little]

These repositories have now been merged, as we discussed. avraw (av11n) 
has been merged into raw (main) and the atticraw (the attic repository) 
has the prior version of each module that was overwritten.

The av repositories themselves have been emptied, but left in place.
masterRepoList.conf has been updated to reflect the removal of these 
repositories.

--Chris

On 11/4/2013 3:50 PM, Chris Little wrote:
> This sounds more or less fine. I'll leave the av repositories on the
> server for a while, but empty, since we've never removed a repository
> before.
>
> I'm not terribly sympathetic towards front ends that can't fail
> gracefully when a network resource is unavailable. Non-local resources
> are unavailable often, and that's something that should be planned for.
> We remove modules from repositories often (either to pull them entirely
> or to move them to another repository) and provide an updated
> mods.tar.gz; we should likewise be able to remove repositories and
> simply provide an updated masterRepoList.conf. I see providing a
> coherent masterRepoList.conf pointing to a set of existing repositories
> pointing to existing modules as the extent of our responsibility. That
> is all to say that if you have a stale cache, you should update or fail
> gracefully.
>
> ZIPs for the main repository aren't generated automatically by us. But
> since this repository is linked from the website, they are inevitably
> generated soon after a module update because users or crawlers download
> them thorugh the intended interface (the webpage). (So technically no,
> but effectively yes, though there's still a small window in which a user
> grabbing from rawzip can get an old version of the module because the
> .conf is more recent than the zip contents.)
>
> --Chris
>
>
> On 10/31/2013 02:02 PM, Martin Denham wrote:
>> Will the migration be done in such a way that front ends with a cached
>> mods.d.tar.gz will not generate errors?  So something like:
>>
>> 1. remove modules from avraw mods.tar.gz
>> 2. add modules to raw mods.tar.gz
>> 3. copy modules from avraw folders to raw folders
>> 4. a month or so later remove modules from avraw
>> 5. later after front ends have removed references to avraw folders
>> remove avraw folders and avraw/mods.tar.gz
>>
>> Regarding (5) can avpackages/rawzip and avraw/mods.tar.gz be left in
>> place for a while, even when empty, otherwise JSword apps (I don't know
>> about Sword apps) which reference these may throw errors.
>>
>> Are zip files automatically generated in packages/rawzip - I have never
>> noticed any missing zips there like I have in avpackages/rawzip?
>>
>> Martin
>>
>>
>> On 28 October 2013 08:29, Chris Little <chrislit at crosswire.org
>> <mailto:chrislit at crosswire.org>> wrote:
>>
>>     LOL. It's nice to see such a level of consensus. :)
>>
>>     I'll wait until at least Sunday 11/2 to act, just in case anyone has
>>     a good argument against merger.
>>
>>     --Chris
>>
>>
>>     On 10/27/2013 7:14 PM, Nic Carter wrote:
>>
>>         Yup! :)
>>
>>         Sent from my phone, hence this email may be short...
>>
>>         On 28 Oct 2013, at 9:38, refdoc at gmx.net <mailto:refdoc at gmx.net>
>>         <mailto:refdoc at gmx.net <mailto:refdoc at gmx.net>>
>>         <refdoc at gmx.net <mailto:refdoc at gmx.net> <mailto:refdoc at gmx.net
>>         <mailto:refdoc at gmx.net>>> wrote:
>>
>>             Seconded
>>
>>             Sent from my HTC
>>
>>             ----- Reply message -----
>>             From: "DM Smith" <dmsmith at crosswire.org
>>             <mailto:dmsmith at crosswire.org> <mailto:dmsmith at crosswire.org
>>             <mailto:dmsmith at crosswire.org>>__>
>>             To: "SWORD Developers' Collaboration Forum"
>>             <sword-devel at crosswire.org <mailto:sword-devel at crosswire.org>
>>             <mailto:sword-devel at crosswire.__org
>>             <mailto:sword-devel at crosswire.org>>>
>>             Cc: "SWORD Developers' Collaboration Forum"
>>             <sword-devel at crosswire.org <mailto:sword-devel at crosswire.org>
>>             <mailto:sword-devel at crosswire.__org
>>             <mailto:sword-devel at crosswire.org>>>
>>             Subject: [sword-devel] merge raw & avraw repos?
>>             Date: Sun, Oct 27, 2013 21:34
>>
>>
>>             Just do it.
>>
>>             Cent from my fone so theer mite be tipos. ;)
>>
>>              > On Oct 27, 2013, at 5:05 AM, Chris Little
>>             <chrislit at crosswire.org <mailto:chrislit at crosswire.org>
>>             <mailto:chrislit at crosswire.org
>>             <mailto:chrislit at crosswire.org>__>> wrote:
>>              >
>>              > It's been over 4 years since the release of Sword 1.6.0,
>>             when av11n
>>             was introduced. I believe that every front end that is still
>>             maintained now supports (to one degree or another) av11n
>>             modules.
>>              >
>>              > Following the release of Sword 1.7.0, I no longer produce
>>             separate
>>             KJV-v11n and av11n versions of modules when producing
>>             updates. Also,
>>             because of changes to the way osis2mod produces modules, all
>>             new Bible
>>             and commentary module releases are tagged as requiring Sword
>>             1.7.0.
>>              >
>>              >
>>              > Would now perhaps be a good time to merge the raw and
>> avraw
>>             repositories (i.e. get rid of the avraw repository and allow
>>             av11n
>>             material in raw)? I don't mind our hosting multiple
>>             repositories, but
>>             the av11n vs. non-av11n distinction is not one that I think
>>             our users
>>             ought to need to worry about. It just brings confusion.
>>              >
>>              > --Chris
>>              >
>>              > _________________________________________________
>>              > sword-devel mailing list: sword-devel at crosswire.org
>>             <mailto:sword-devel at crosswire.org>
>>             <mailto:sword-devel at crosswire.__org
>>             <mailto:sword-devel at crosswire.org>>
>>
>>              > http://www.crosswire.org/__mailman/listinfo/sword-devel
>>             <http://www.crosswire.org/mailman/listinfo/sword-devel>
>>              > Instructions to unsubscribe/change your settings at above
>>             page
>>
>>             _________________________________________________
>>             sword-devel mailing list: sword-devel at crosswire.org
>>             <mailto:sword-devel at crosswire.org>
>>             <mailto:sword-devel at crosswire.__org
>>             <mailto:sword-devel at crosswire.org>>
>>
>>             http://www.crosswire.org/__mailman/listinfo/sword-devel
>>             <http://www.crosswire.org/mailman/listinfo/sword-devel>
>>             Instructions to unsubscribe/change your settings at above
>> page
>>             _________________________________________________
>>             sword-devel mailing list: sword-devel at crosswire.org
>>             <mailto:sword-devel at crosswire.org>
>>             <mailto:sword-devel at crosswire.__org
>>             <mailto:sword-devel at crosswire.org>>
>>
>>             http://www.crosswire.org/__mailman/listinfo/sword-devel
>>             <http://www.crosswire.org/mailman/listinfo/sword-devel>
>>             Instructions to unsubscribe/change your settings at above
>> page
>>
>>
>>
>>         _________________________________________________
>>         sword-devel mailing list: sword-devel at crosswire.org
>>         <mailto:sword-devel at crosswire.org>
>>         http://www.crosswire.org/__mailman/listinfo/sword-devel
>>         <http://www.crosswire.org/mailman/listinfo/sword-devel>
>>         Instructions to unsubscribe/change your settings at above page
>>
>>
>>
>>     _________________________________________________
>>     sword-devel mailing list: sword-devel at crosswire.org
>>     <mailto:sword-devel at crosswire.org>
>>     http://www.crosswire.org/__mailman/listinfo/sword-devel
>>     <http://www.crosswire.org/mailman/listinfo/sword-devel>
>>     Instructions to unsubscribe/change your settings at above page
>>
>>
>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at 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 at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page