Am 06.10.2009 um 04:38 schrieb Chris Little:
Ok, I'm certainly amenable to removing experimental from
masterRepoList.conf.
I had imagined that the name "experimental" itself would discourage
people from adding this repo and expecting useful content. My
concern and request that users not be directed to this repository
were based on a practice that has become more common lately, in
which a user writes to sword-support asking for a module in some
language (e.g. Welsh or Japanese) and is directed to the beta
module. I don't want people who write to complain about the RST
module to be directed to the RusSynodal module that may replace it
since it won't work without Sword 1.6.1 and a front end that can use
av11n.
I don't mind if users download the content we have in the
experimental repo, provided they don't expect it to work or be of
decent quality.
I'd say it can stay in the master repo list.
If user see this repo name and switch on their brains it doesn't need
any more clarification.
Is there still a consensus that experimental should be removed from
masterRepoList.conf? We could add a note field to that .conf and
label it as "for developers only". A note field might also help
clarify the purpose of the bible.org repo that causes some
confusion. (This would of course not be a useable field prior to
1.6.1--but I assume that's coming fairly soon.)
--Chris
Nic Carter wrote:
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 :)
ybic
nic... :)
On 06/10/2009, at 9:24 AM, Matthew Talbert wrote:
On Mon, Oct 5, 2009 at 6:15 PM, Chris Little
<chris...@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
list.
This is a very good idea.
It's also in the masterRepoList.conf file, for those of you whose
install
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.
Matthew
_______________________________________________
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
_______________________________________________
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
