This will allow creation of packages (debian/ubuntu, zip, and tarball) from patch releases, which will work correctly when a user is using them to upgrade from a prior OpenEMR version.
This fix will require another patch and another full round of testing before the deb/ubuntu package can be released…
(I am hoping that I am beginning to see some light at the end of this rather long and windy tunnel)
There is no deadline except that which has been self-imposed; so slow and steady is just fine. Unlike MU2.
Those who have installed the package in the past and are new to Linux, don’t know enough to re-configure the package to make it work in LM 17. Those with technical knowledge to adapt to the new distributions don’t need the package, while those with less expertise continue working with the older versions.
If the tunnel is only bi-directional, that suggests less complexity than previously anticipated. Young folks are not prone to Keratoconjunctivitis Sicca. No goggles will be needed to protect from the wind.
Beginning of the end would be better, but end of the beginning is good, too.
A newly built package with above fixes worked perfectly on all testing in Ubuntu 14.04. Still need to test on all OS’s in addition to the zip and tarball, but I think we may have it
All the thanks should go to Brady. None of my doings in this. I am still
hard at work trying to squish our distro into Debian standards. Now that
we have a patch 7 will apply that to the 4.1.2p6 package that I have and
continue figuring out why the deprecated Smarty Calendar stuff doesn’t like
it when I place the code in the /usr/share/openemr dir and symlink to the
writable dirs in /var/lib.
Zend was just incorporated into the development codebase. This brings yet another host of fun things to configure and deal with for packaging(I did some basic stuff in the current deb scripts, but still need to work out how to best deal with apache configuration (turn on rewrite module and set up AllowOveride in a secure fashion)). Details can be found here: http://www.open-emr.org/wiki/index.php/Zend
Meaningful Use 2 deadlines are quickly approaching, so guessing lots of other stuff will be soon coming into the codebase. You may want to consider working on the development codebase in preparation for a 4.1.3 release(I honestly have no clue when this will be released, though).
Brady - Thanks for the heads up. I think the easiest way to incorporate the changes is to put the options right in the apache conf file. The one would just enable with a2enconf - or if using the site with a2ensite I think is the other.
I will finish off with the 4.1.2 code since it has the bulk of all out problems (embedded code, minified JavaScript, files that ref non-available interpreters, etc). Everything that I fix in the current version will also need to be fixed in 4.1.3 but it’s much easier once you have done it once.
Zend was just incorporated into the development codebase. This brings yet another host of fun things to configure and deal with for packaging(I did some basic stuff in the current deb scripts, but still need to work out how to best deal with apache configuration (turn on rewrite module and set up AllowOveride in a secure fashion)). Details can be found here: Zend - OpenEMR Project Wiki
Meaningful Use 2 deadlines are quickly approaching, so guessing lots of other stuff will be soon coming into the codebase. You may want to consider working on the development codebase in preparation for a 4.1.3 release(I honestly have no clue when this will be released, though).
Unable to confirm issue in 6 above. I just installed the deb package via new Mint 17 install and the backup script worked fine(took about a minute for a new install).
