[sword-devel] experimental repository & new module release procedures
niccarter at mac.com
Mon Oct 5 18:47:38 MST 2009
Can I second what Matthew said?
The experimental modules repo sounds great (& I can't wait to see how
broken our app is for some of those mods!), but access to it should be
something where the user has to specifically know about it & manually
add it as an install source? And hence not suddenly available if the
user does an InstallMgr->refreshRemoteSourceConfiguration() ? :)
Thanks for your hard work :)
On 06/10/2009, at 9:24 AM, Matthew Talbert wrote:
> On Mon, Oct 5, 2009 at 6:15 PM, Chris Little
> <chrislit at crosswire.org> wrote:
>> I created a new repository over the weekend for experimental
>> modules. This
>> repo is intended for front end developers. PLEASE DO NOT DIRECT
>> USERS TO
>> THIS REPOSITORY. It is not for casual users or even very many
>> people on this
> This is a very good idea.
>> It's also in the masterRepoList.conf file, for those of you whose
>> managers have been updated to use this facility.
> I'm not sure about this. As it is, any user using Xiphos 3.1 or later
> will now automatically get this repo on a refresh. To prevent this,
> we'd have to filter out this specific repo as we're refreshing.
> Especially with Karmic soon to be released with 3.1, that means there
> will be tons of end-users who suddenly have this repo automatically
> and there's nothing we can do about it.
> Everything else sounds good.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel