I am currently working at University of Transkei in Umtata, South Africa,> and we are looking to use care2x for hospitals in Africa.
That is very interesting as we have people in nearby Mozambique (I have been both in Mozambique and in the Transkei province of ZA, so I know that it is not so near...) that would also like to try Care2x, but who do not have the knowledge to do so.
I am talking about Dr. Jose Casanovas from the Maputo's University Medicine Faculty and Maputo's Military Hospital.
> My main interest though is
telemedicine --> ipath.sourceforge.net]
This is also very interesting. Telemedicine and the knowledge from the ipath project could be an added value to the Care2x project also.
What is the reason. Does Tille not want to keep supporting the debian package for care2x?
No, there is a simpler reason, there is no Care2x.deb package yet...
If there is really interest in having care2x as a debian package, I guess I could volunteer to maintain that.
It would be a major step forward for the project if someone could help to setup a Care2x Debian package.
Have you seen the Care2x setup and install routines?
How different would it be for the project "ease-of-use", if we had a means of installing and configuring care2x and all its relations, with a simple and reliable "apt-get install care2x".
I would only need some guidance concerning which files would go into> a stable and a testing release ....
In the Debian sense there is no "stable" Care2x yet. Which is not to be confused with the actual Care2x 1.1 being called stable.
As we know Debian's stable, unstable and testing just have precise meanings.
At this stage of the Care2x project it would be nice if we could have it included in the "unstable" branch of the Debian distro.
> packaging .deb otherwise is not too complex.
To us it is too complex. Nobody was able to it up until now.
If we could get it done in 6 months it would be a major leap for the project.
But it is one of the greatnesses of Open Source software, whatever the complexity of any given problem, there will be some person, somewhere, that will be able to easily solve it. To that person it will be obvious...
I did it a try using the bellow methodology. Obviously it gave no results, so I do not know if it is useful at all. It only seems reasonable.
So, take a look at it and tell me if it is of any use:
1. In order to install Care2x, we need some pre-installed (pre depends on) packages:
1.1. Apache web server with modules: SSL, GD, MM
1.2. MySQL DBMS
1.3. PHP with support for the above Apache modules
2. Care2x is an Hospital Information System, so security will always be of great concern. It would be most desirable to have Care2x code and all that ancillary programs installed without root privileges. It would be desirable to have read/write access only under some kind of user access. If we find it too difficult I guess that we could drop it for now.
3. I did find a Debian package that uses similar ancillary programs and that is configured with similar concerns as Care2x. It is the DRUPAL content management system. It is a small .deb package (395 Kb). It has some clever shell routines to install and copy/move the code around the Debian filesystem. It also has great concerns about security and deals with it effectively. So, if I am not wrong, it would be much easier to use it as a template for our own package. DRUPAL may be found at:
http://packages.debian.org/unstable/web/drupal.html
And concerning Antas remark, I guess having a .deb package does not undermine the integrity of the source on sf.
Perhaps I was misunderstood here. I am portuguese and my english isn't always the best and sometimes it gets out as portuguese dressed with english words. So please be patient with me.
What I was trying to say was that, perhaps it would be easier to get the attention of the other Care2x developers, if we kept the development of the Care2x Debian package inside the Care2x CVS tree at Sourceforge instead at the proposed tree at the shown Tille's page. As we already go there, day in day out, to look for new developments it would be easier to give a quick look at the improvements at the .deb package.
Any package like CvsGui (http://cvsgui.sourceforge.net/) makes it easier to "point&click", "drag&drop", "copy&paste" code from the sourceforge CVS.
We would have the best of both worlds: a Debian package (Amazing! I cannot believe it yet!) and access to it (download/change/upload) from our old faithful Sourceforge CVS. Of course, once ready, it would be up to you the world's Debian mirrors
I am forwarding this email to Elpidio to get his personal attention to this matter.
Best Regards,
J. Antas, M.D.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
