Difference between revisions of "Ubuntu-Debian Package Developers Page"

From OpenEMR Project Wiki
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
:*Re-optimize the php settings (drop the ones that are no longer needed and optimize the others)
==Ongoing work in 4.1.3 version==
:*Need to make next package compatible with the multisite module
*Need to get things to work with Zend:
:::*securing the patient document directories over all sites in apache
# <strike>Writable interface/modules/zend_modules/config/application.config.php file</strike>
:::*copying over all sites instances during an upgrade
# Set up apache. See this thread for details:
:::*upgrading all site instances database/acl during an upgrade
https://sourceforge.net/p/openemr/discussion/202506/thread/b515b5bd/
:*May try to prepare the next official package (4.1.1-1) to get submitted to debian and ubuntu.
 
:::*'''STEP ONE''': Ensure that modifying the php configuration and apache config file is ok for official packages.
==Ongoing work in 4.1.2 version==
:::*'''STEP TWO''': Submit the official package (not the cvs package) to debian and ubuntu.
*Current am working on packaging 4.1.2 patch 5 with help from the Debian Med mailing list.  Top issues that we have are:
** Filesystem of package is not compliant with Debian and would need to be modified to comply with:
::<code>/etc/openemr</code> - Conf files '''Apache2, MySQL, PHP5'''
::<code>/usr/sbin</code> - Scripts to help secure/configure application after install (PHPMyAdmin has pma-secure, pma-configure)
::<code>/usr/share/openemr</code> - PHP script code (non-writtable per FHS standard)
::<code>/usr/share/doc/openemr</code> - Generated code documentation (I don't think we have any)
::<code>/usr/share/doc-base/openemr</code> - Doc-base doc
::<code>/usr/share/man/man8</code> - Man page (PHPMyAdmin places there's in man8 and seems reasonable)
::<code>/var/lib/openemr</code> - Writtable dirs/files
::<code>/var/lib/openemr/sites/*/documents</code>
::<code>/var/lib/openemr/sites/*/edi</code>
::<code>/var/lib/openemr/sites/*/era</code>
::<code>/var/lib/openemr/sites/*/letter_templates</code>
::<code>/var/lib/openemr/gacl/admin/templates_c</code>
::<code>/var/lib/openemr/interface/main/calendar/modules/PostCalendar/pntemplates/complied</code>
::<code>/var/lib/openemr/interface/main/calendar/modules/PostCalendar/pntemplates/cache</code>
 
Current issues:
# Our code is currently held under /var/www
# Our configuration is almost exclusively held in some directory underneath /var/www well.
# globals.php is the typical file that holds all the PATHs and other variables that most other scripts rely on to orient themselves on the system.  To be Debian compliant there will most likely need to be some modifications.
# We include several tools that are already packaged with Debian (phpGACL, phpmyadmin) and these should be removed and required dependencies if we want to include them
 
Goals:
# <strike>Create Alioth Account for Debian and confirm that have ssh to Alioth for git repo, etc.</strike>
# <strike>Create dummy package with openemr-4.1.2 so that we can start reworking things.</strike>
# With upstream tar ball start patching globals.php such that it might actually conform to the above structure using quilt
# <strike>Try to figure out what 'build' system PHPMyAdmin source uses since they package ok with debhelper tools (is it Makefile, etc)</strike> - No build system just a complicated rules and install file, will need to replicate/change for our project.
 


[[Category:Ubuntu Package]][[Category:Debian Package]][[Category:Developer Guide]]
[[Category:Ubuntu Package]][[Category:Debian Package]][[Category:Developer Guide]]

Latest revision as of 21:56, 28 June 2014

Ongoing work in 4.1.3 version

  • Need to get things to work with Zend:
  1. Writable interface/modules/zend_modules/config/application.config.php file
  2. Set up apache. See this thread for details:

https://sourceforge.net/p/openemr/discussion/202506/thread/b515b5bd/

Ongoing work in 4.1.2 version

  • Current am working on packaging 4.1.2 patch 5 with help from the Debian Med mailing list. Top issues that we have are:
    • Filesystem of package is not compliant with Debian and would need to be modified to comply with:
/etc/openemr - Conf files Apache2, MySQL, PHP5
/usr/sbin - Scripts to help secure/configure application after install (PHPMyAdmin has pma-secure, pma-configure)
/usr/share/openemr - PHP script code (non-writtable per FHS standard)
/usr/share/doc/openemr - Generated code documentation (I don't think we have any)
/usr/share/doc-base/openemr - Doc-base doc
/usr/share/man/man8 - Man page (PHPMyAdmin places there's in man8 and seems reasonable)
/var/lib/openemr - Writtable dirs/files
/var/lib/openemr/sites/*/documents
/var/lib/openemr/sites/*/edi
/var/lib/openemr/sites/*/era
/var/lib/openemr/sites/*/letter_templates
/var/lib/openemr/gacl/admin/templates_c
/var/lib/openemr/interface/main/calendar/modules/PostCalendar/pntemplates/complied
/var/lib/openemr/interface/main/calendar/modules/PostCalendar/pntemplates/cache

Current issues:

  1. Our code is currently held under /var/www
  2. Our configuration is almost exclusively held in some directory underneath /var/www well.
  3. globals.php is the typical file that holds all the PATHs and other variables that most other scripts rely on to orient themselves on the system. To be Debian compliant there will most likely need to be some modifications.
  4. We include several tools that are already packaged with Debian (phpGACL, phpmyadmin) and these should be removed and required dependencies if we want to include them

Goals:

  1. Create Alioth Account for Debian and confirm that have ssh to Alioth for git repo, etc.
  2. Create dummy package with openemr-4.1.2 so that we can start reworking things.
  3. With upstream tar ball start patching globals.php such that it might actually conform to the above structure using quilt
  4. Try to figure out what 'build' system PHPMyAdmin source uses since they package ok with debhelper tools (is it Makefile, etc) - No build system just a complicated rules and install file, will need to replicate/change for our project.