Patchtool: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
No edit summary
(Source folder PetraTools was renamed to BuildTools)
Line 4: Line 4:
* see in the OpenPetra.org bazaar repository:
* see in the OpenPetra.org bazaar repository:
** [http://bazaar.launchpad.net/~openpetracore/openpetraorg/trunkhosted/view/head:/csharp/ICT/Common/IO/PatchTools.cs managed bsdiff library]
** [http://bazaar.launchpad.net/~openpetracore/openpetraorg/trunkhosted/view/head:/csharp/ICT/Common/IO/PatchTools.cs managed bsdiff library]
** [http://bazaar.launchpad.net/~openpetracore/openpetraorg/trunkhosted/files/head:/csharp/ICT/PetraTools/PatchTool/ OpenPetra.org PatchTool]
** [http://bazaar.launchpad.net/~openpetracore/openpetraorg/trunkhosted/files/head:/csharp/ICT/BuildTools/PatchTool/ OpenPetra.org PatchTool]
 
== description ==
== description ==
* for creating a patch, we need a tar.gz file from the previous release and the current release
* for creating a patch, we need a tar.gz file from the previous release and the current release

Revision as of 16:14, 9 January 2017

sources

description

  • for creating a patch, we need a tar.gz file from the previous release and the current release
  • each release contains a version.txt file in the bin directory, to be able to determine the currently installed version
  • individual files can be replaced in a production environment, as long as the original file is stored with the .orig extension
  • for building the patch, we use the original bsdiff program which is written in C. It is available for Windows and Linux. It is much faster as a version we wrote in Managed Code, though that is probably due to lack of time and knowledge how to make the algorithm work fast in C# as well.
  • for applying the patch, our managed code works quite well, so we don't require an additional binary on the production machines