Re: [Gnumed-devel] default workplace in tarballs

[Sebastian Hilbert]

Am Donnerstag 08 Juli 2010, 09:59:16 schrieb Jim Busser:
> On 2010-07-08, at 12:29 AM, Karsten Hilbert wrote:
> > I guess I need to rack my brain for remembering some
> > arguments.
> 
> If the strongest argument is to not disturb the (small number of
> individuals) who already have some value in their .config file...
> 
> - I was thinking we should supply something more than a single plugin to
> all of the people who would newly try GNUmed but who risk to wrongly
> dismiss it out of annoyance. I am talking about people who may download it
> from tarball or source and who might like to get a sense of it without
> having all the pain of all of the configuration.
>
Snip ... This has been discussed many moons ago and the reason was that the 
Mac back then crashed some plugins. If one plugin crashed GNUmed would not 
load. It was therefore decided that only one plugin will be loaded by default 
to make debugging possible apart from fiddling with the database to unset some 
plugins.

This ought to stay the way it is. And here is why.

1) The above is still true
2) anyone downlaoding source or git can be considered clever enough to enable 
more plugins
2) a note can be added to the inbox to notify the user that there are more 
plugins
3) When we roll packages (at least Windows and openSUSE, Fedora) the 
maintainers of these packages set the workplace to GNUmed Default.

No Mac user in the world will ever run from source and not be able to set this 
information. The maintainer of a future Mac package will make sure that for 
drive-by users GNUmed Default is enabled.

The minute someone contacts us complaining that he is a regular user and tried 
from source and there is only one plugin we might rethink that issue. Until 
then it is up to the maintainer.

BTW Most drive-by users use Debian/Ubuntu and Windows. Both systems have all 
plugins available.

Sebastian