[Debian-med-packaging] Bug#707639: Bug#707639: gnuhealth: System user for the server

[Emilien Klein]

2014-03-27 12:46 GMT+01:00 Mathias Behrle <mathiasb at m9s.biz>:
> * Emilien Klein: " Re: [Debian-med-packaging] Bug#707639: gnuhealth: System
>   user for the server" (Wed, 26 Mar 2014 22:39:05 +0100):
>
>> The GNU Health package runs its own dedicated Tryton server, under
>> that gnuhealth user, unoconv would thus run under the same user as the
>> Tryton server.
>
> I think you are missing the point.

It's because I'm coming from a different angle than you. Read on ;)

> Provided you are running a tryton-server and
> a gnuhealth-server under different users on the same machine, it will be
> painful (read: impossible AFAIK) to run a unoconv service for both of them or
> for each of them.

You are correct that having 2 running Tryton servers is not
helpful/wise. That is why having a service-less Tryton package would
be very helpful in this case (cf link in my previous post)

To me, if a user is going to install GNU Health, they do it for
medical reasons. They will also take care of the ERP side of running
the hospital using Tryton, but they won't be running a separate Tryton
server for that. They'll do it in the same Tryton server that is
running for GNU Health.

As mentioned, I consider the Tryton server package to be in a
"broken/unusable" state right after installation. I want the GNU
Health package to be usable right out of the box, and be able to
assist the users in all steps related to upgrades (such as updating
the database models, possibly removing unused tables, etc.).

I can only do that if the database is managed by the Debian package.
To manage the database, it needs to be created by the gnuhealth
package. As I can't fiddle with files installed by the Tryton package
(e.g. /etc/trytond.conf) as that is obviously against Debian packaging
conventions. This ensues that I need to have the ability to have a
gnuhealth user that owns the database, and run a Tryton server under
that user so that it can access the database.

>> I will close this issue as the current situation is the best for the
>> Debian users of GNU Health.
>> You are obviously free to add more details and argument your position,
>> should you think this presents major issues for Debian or its users.
>
> Done. I don't think the current way is the best way to do it. I still can't see
> the added value in using an additional system user compared to the
> complications it can cause.

Does my explanation below help you understand my point of view?
The core of the issue is not so much the dedicated user. It's the fact
that in the current situation we have 2 running Tryton servers. The
GNU Health-generated one is a precondition for the ease-of-use that I
want to provide to my users.

If there was a service-less tryton-server package, this issue wouldn't
be one. Would you be willing to accept a patch from me to do that?

    +Emilien