How to Package Rifidi Edge - Revision history

Bppause: /* Prerequisites */

2016-08-30T09:45:11Z

‎Prerequisites

Bppause: /* Steps */

2016-08-30T09:44:52Z

‎Steps

Bppause: /* Prerequisites */

2016-08-30T09:44:37Z

‎Prerequisites

Bppause: /* Prerequisites */

2016-08-30T09:33:21Z

‎Prerequisites

Bppause at 11:30, 4 November 2014

2014-11-04T11:30:06Z

Matt at 04:15, 4 November 2014

2014-11-04T04:15:22Z

Matt at 03:46, 4 November 2014

2014-11-04T03:46:02Z

Matt at 03:36, 4 November 2014

2014-11-04T03:36:10Z

Matt at 03:08, 4 November 2014

2014-11-04T03:08:00Z

Matt: /* Introduction */

2014-11-04T02:54:38Z

‎Introduction

@@ Line 47: / Line 47: @@
 *2. Make sure the debian file itself isn't in the SDK, as it will make the SDK much too large.
 *3. Make sure you don't have anything non-standard in the RifidiHome folder, and make sure the launch file and launch file VM args are correct.
-*4. Make sure the SDK  is disconnected from SVN.
+*4. Make sure the SDK  is disconnected from Github.
 ==Steps==
 *1. Make sure the SDK is working, then zip it up.  It is ready for release.

@@ Line 24: / Line 24: @@
 *3. Navigate to the SDK folder in the terminal and type 'sh build.sh'.  DO NOT use sudo.
 *4. The deb will show up in sdk/rifidi/debian/Debian-packages
-*5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)".  Test it and make sure everything is correct.  If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN).
+*5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)".  Test it and make sure everything is correct.  If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from Github).
 =Server Only Zip=
 ==Prerequisites==

@@ Line 17: / Line 17: @@
 *3. bundles.info is very easy to get wrong.  Test the deb as soon as you export it for the first time, and make sure all the bundles you are expecting to show up show up with the "ss" command.  Debug and fix any that aren't working, fix the bundles.info in the SDK and rebuild.
 *4. Make sure the version numbers are incremented in "SDK/version.txt", "SDK/rifidi/usr/local/sbin/rifidi/version.txt", and "SDK/rifidi/debian/DEBIAN/control".
-*5. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from SVN.
+*5. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from Github.
 ==Steps==
 *1. Make sure you have a new, fully updated SDK in your workspace.

@@ Line 33: / Line 33: @@
 ==Prerequisites==
 *1. You need to be on windows to make the windows installer.
-*2. You need the "/install" folder from the edge SVN.
+*2. You need the "/install" folder from the edge Github.
 *3. You need Inno Setup.
 *4. You'll need the "client" folder from a previous windows install, and the contents of the zip file in a folder called "server".  Put them in the same folder, and modify the inno file in the install directory to point to that folder.  Also make sure the inno install file is pointed at the installer assets, and make sure the version in the inno install file is correct.
 ==Steps==
 *1. Once the inno file is pointed at the correct place, compile and build the Inno file from Inno Setup.

@@ Line 3: / Line 3: @@
 It is best to export the versions in this order for release:
-. Deb
+*1. Deb
-. Server only
+*2. Server only
-. Windows Installer
+*3. Windows Installer
-. SDK
+*4. SDK
 You will need a windows and linux machine (or virtual machine) to export and test.  Dropbox is invaluable for this purpose, as it allows you to easily share the files across different machines.
@@ Line 13: / Line 13: @@
 =Deb=
 ==Prerequisites==
-. You need to be on linux to build the Deb.
+*1. You need to be on linux to build the Deb.
-. The docs, jars, bundles,info, rifidiserver.ini and rifidi-server linux executable must all be correct before release.  Check them all before and after you export the deb or you will need to export it again.
+*2. The docs, jars, bundles,info, rifidiserver.ini and rifidi-server linux executable must all be correct before release.  Check them all before and after you export the deb or you will need to export it again.
-. bundles.info is very easy to get wrong.  Test the deb as soon as you export it for the first time, and make sure all the bundles you are expecting to show up show up with the "ss" command.  Debug and fix any that aren't working, fix the bundles.info in the SDK and rebuild.
+*3. bundles.info is very easy to get wrong.  Test the deb as soon as you export it for the first time, and make sure all the bundles you are expecting to show up show up with the "ss" command.  Debug and fix any that aren't working, fix the bundles.info in the SDK and rebuild.
-. Make sure the version numbers are incremented in "SDK/version.txt", "SDK/rifidi/usr/local/sbin/rifidi/version.txt", and "SDK/rifidi/debian/DEBIAN/control".
+*4. Make sure the version numbers are incremented in "SDK/version.txt", "SDK/rifidi/usr/local/sbin/rifidi/version.txt", and "SDK/rifidi/debian/DEBIAN/control".
-. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from SVN.
+*5. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from SVN.
 ==Steps==
-. Make sure you have a new, fully updated SDK in your workspace.
+*1. Make sure you have a new, fully updated SDK in your workspace.
-. Disconnect the SDK project from SVN.  Delete the SVN metadata.  If all the exported documents are way too big, you forgot to do this step.
+*2. Disconnect the SDK project from SVN.  Delete the SVN metadata.  If all the exported documents are way too big, you forgot to do this step.
-. Navigate to the SDK folder in the terminal and type 'sh build.sh'.  DO NOT use sudo.
+*3. Navigate to the SDK folder in the terminal and type 'sh build.sh'.  DO NOT use sudo.
-. The deb will show up in sdk/rifidi/debian/Debian-packages
+*4. The deb will show up in sdk/rifidi/debian/Debian-packages
-. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)".  Test it and make sure everything is correct.  If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN).
+*5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)".  Test it and make sure everything is correct.  If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN).
 =Server Only Zip=
 ==Prerequisites==
-. You'll need a debian package you are satisfied is working correctly to make the zip.
+*1. You'll need a debian package you are satisfied is working correctly to make the zip.
 ==Steps==
-. Open the deb with an archive tool and extract the "rifidi" folder.
+*1. Open the deb with an archive tool and extract the "rifidi" folder.
-. Zip up the folder to a 7zip file with the name "RifidiEdge-XXX-server_only.7z", where XXX is the version number, like "3.1.0".
+*2. Zip up the folder to a 7zip file with the name "RifidiEdge-XXX-server_only.7z", where XXX is the version number, like "3.1.0".
 =Windows Installer=
 ==Prerequisites==
-. You need to be on windows to make the windows installer.
+*1. You need to be on windows to make the windows installer.
-. You need the "/install" folder from the edge SVN.
+*2. You need the "/install" folder from the edge SVN.
-. You need Inno Setup.
+*3. You need Inno Setup.
-. You'll need the "client" folder from a previous windows install, and the contents of the zip file in a folder called "server".  Put them in the same folder, and modify the inno file in the install directory to point to that folder.  Also make sure the inno install file is pointed at the installer assets, and make sure the version in the inno install file is correct.
+*4. You'll need the "client" folder from a previous windows install, and the contents of the zip file in a folder called "server".  Put them in the same folder, and modify the inno file in the install directory to point to that folder.  Also make sure the inno install file is pointed at the installer assets, and make sure the version in the inno install file is correct.
 ==Steps==
-. Once the inno file is pointed at the correct place, compile and build the Inno file from Inno Setup.
+*1. Once the inno file is pointed at the correct place, compile and build the Inno file from Inno Setup.
-. Test the installer and make sure everything is working.
+*2. Test the installer and make sure everything is working.
 =SDK=
 ==Prerequisites==
-. You need the SDK folder from when you built the deb.
+*1. You need the SDK folder from when you built the deb.
-. Make sure the debian file itself isn't in the SDK, as it will make the SDK much too large.
+*2. Make sure the debian file itself isn't in the SDK, as it will make the SDK much too large.
-. Make sure you don't have anything non-standard in the RifidiHome folder, and make sure the launch file and launch file VM args are correct.
+*3. Make sure you don't have anything non-standard in the RifidiHome folder, and make sure the launch file and launch file VM args are correct.
-. Make sure the SDK  is disconnected from SVN.
+*4. Make sure the SDK  is disconnected from SVN.
 ==Steps==
-. Make sure the SDK is working, then zip it up.  It is ready for release.
+*1. Make sure the SDK is working, then zip it up.  It is ready for release.

@@ Line 1: / Line 1: @@
 =Introduction=
-These are the prerequisites and steps for packaing teh Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer
+These are the prerequisites and steps for packaing the Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer
 =SDK=
 ==Prerequisites==