Unix/Linux Packages - Revision history

Manus: Replaced origo.ethz.ch by eiffel.com in SVN URL

2012-06-04T21:08:09Z

Replaced origo.ethz.ch by eiffel.com in SVN URL

← Older revision		Revision as of 21:08, 4 June 2012
Line 18:		Line 18:
	Make sure $ISE_EIFFEL and $ISE_PLATFORM are pointing to the delivery you want to make a package for. The version of EiffelStudio will automatically be detected so your package will be named correctly and also contain all information related to the delivery $ISE_EIFFEL points to.		Make sure $ISE_EIFFEL and $ISE_PLATFORM are pointing to the delivery you want to make a package for. The version of EiffelStudio will automatically be detected so your package will be named correctly and also contain all information related to the delivery $ISE_EIFFEL points to.

	Regardless which distribution you want to create a package for, you will need a directory called '''packaging''' and a script called '''make_unix_layout''' from https://svn.~~origo~~.~~ethz.ch~~/eiffelstudio/trunk/Delivery/scripts/unix/. The '''packaging''' directory contains build related files for all distribution. '''make_unix_layout''' is used by the packaging scripts to create the final unix layout for EiffelStudio (the way it will be installed later on the end user's system).		Regardless which distribution you want to create a package for, you will need a directory called '''packaging''' and a script called '''make_unix_layout''' from https://svn.eiffel.com/eiffelstudio/trunk/Src/Delivery/scripts/unix/. The '''packaging''' directory contains build related files for all distribution. '''make_unix_layout''' is used by the packaging scripts to create the final unix layout for EiffelStudio (the way it will be installed later on the end user's system).

	In a terminal, type the following commands in the directory you want to create your package(s). In general you do not need root access to build the packages.		In a terminal, type the following commands in the directory you want to create your package(s). In general you do not need root access to build the packages.

	<pre>		<pre>
	export SVNURL=https://svn.~~origo~~.~~ethz.ch~~/eiffelstudio/trunk		export SVNURL=https://svn.eiffel.com/eiffelstudio/trunk/Src
	svn export $SVNURL/Delivery/scripts/unix/packaging		svn export $SVNURL/Delivery/scripts/unix/packaging
	svn export $SVNURL/Delivery/scripts/unix/make_unix_layout		svn export $SVNURL/Delivery/scripts/unix/make_unix_layout

Manus: Updated the command line arguments

2011-10-29T00:07:44Z

Updated the command line arguments

← Older revision		Revision as of 00:07, 29 October 2011
Line 77:		Line 77:
	== Creating the packages ==		== Creating the packages ==

	Creating the package itself is fairly simple. Depending on which distribution you want to build a package for, type one of the following commands.		Creating the package itself is fairly simple. Depending on which distribution you want to build a package for, type one of the following commands where '''ISE_PLATFORM''', '''ISE_EIFFEL''' and '''architecture''' have to be replaced by the corresponding value corresponding to your platform and architecture.

	For a debian (.deb) package:		For a debian (.deb) package:

	<pre>		<pre>
	./make_debian_package		./make_debian_package $ISE_PLATFORM $ISE_EIFFEL [arch]
	</pre>		</pre>

Line 88:		Line 88:

	<pre>		<pre>
	./make_rpm_package		./make_rpm_package $ISE_PLATFORM $ISE_EIFFEL
	</pre>		</pre>

Line 94:		Line 94:

	<pre>		<pre>
	./make_svr_package		./make_svr_package $ISE_PLATFORM $ISE_EIFFEL
	</pre>		</pre>

Arnofiva at 16:17, 30 May 2008

2008-05-30T16:17:58Z

← Older revision		Revision as of 16:17, 30 May 2008
Line 1:		Line 1:
	[[Category:Build Scripts]]		[[Category:Build Scripts]]

	~~For building~~ binary ~~installation~~ packages for different Linux/~~Unix distribution you can use the scripts '''make_debian_package''', '''make_rpm_package''' and '''make_svr_package'''~~.		{{Note\|This pages describes how to build binary packages of EiffelStudio for different Unix/Linux distributions. If you are looking for already built packages see [[Unix/Linux Repositories]].}}


	== Introduction ==		== Introduction ==

	This is a step by step manual on how to create ~~such~~ packages with ~~these scripts~~. Since the source is the same for all distributions, the resulting packages are not distribution specific. This means you should be able to install e.g. a resulting .deb package on Debian and Ubuntu.		This is a step by step manual on how to create binary EiffelStudio packages with '''make_debian_package''', '''make_rpm_package''' and '''make_svr_package'''. Since the source is the same for all distributions, the resulting packages are not distribution specific. This means you should be able to install e.g. a resulting .deb package on any Debian and Ubuntu distribution.
	In general the scripts take an existing EiffelStudio delivery, copy all files to a temporary Unix root directory and call the packaging tools for the specific distribution.		In general the scripts take an existing EiffelStudio delivery, copy all files to a temporary Unix root directory and call the packaging tools for the specific distribution.

Line 196:		Line 197:
	== See also ==		== See also ==

			* [[Unix/Linux Repositories]]
	* [[LinuxUnixLayout]]		* [[LinuxUnixLayout]]

Manus: Added instruction to import a private key on the system.

2008-05-29T23:14:02Z

Added instruction to import a private key on the system.

← Older revision		Revision as of 23:14, 29 May 2008
Line 105:		Line 105:

	So far signing is only supported for RPM packages. '''make_rpm_package''' will automatically try to sign the package if '''gpg''' is available on your system. Also you will need to set '''$KEY''' and '''$PASS_PHRASE''' in '''packaging/config.sh''' with the identifier/pass phrase of your private key.		So far signing is only supported for RPM packages. '''make_rpm_package''' will automatically try to sign the package if '''gpg''' is available on your system. Also you will need to set '''$KEY''' and '''$PASS_PHRASE''' in '''packaging/config.sh''' with the identifier/pass phrase of your private key.

			Do not forget to import your private key by using:
			<pre>gpg --import my_private_key.gpg</pre>

	== Verifying packages (optional) ==		== Verifying packages (optional) ==

Manus: /* RPM */

2008-05-29T23:09:55Z

RPM

← Older revision		Revision as of 23:09, 29 May 2008
Line 58:		Line 58:
	Sometimes, RPM does not have <code>rpmbuild</code> installed. Usually you can install it be typing this into a root shell:		Sometimes, RPM does not have <code>rpmbuild</code> installed. Usually you can install it be typing this into a root shell:

	<pre>		<pre>yum install rpm-build</pre>
	yum install rpm-build
	</pre>		On a debian system:

			<pre>sudo apt-get install rpm</pre>

	=== UNIX ===		=== UNIX ===

Manus: moved `trunk' part to the definition of SVNURL so that it can be done using the various branches

2008-05-29T22:44:48Z

moved `trunk' part to the definition of SVNURL so that it can be done using the various branches

← Older revision		Revision as of 22:44, 29 May 2008
Line 22:		Line 22:

	<pre>		<pre>
	export SVNURL=https://svn.origo.ethz.ch/eiffelstudio		export SVNURL=https://svn.origo.ethz.ch/eiffelstudio/trunk
	svn export $SVNURL~~/trunk~~/Delivery/scripts/unix/packaging		svn export $SVNURL/Delivery/scripts/unix/packaging
	svn export $SVNURL~~/trunk~~/Delivery/scripts/unix/make_unix_layout		svn export $SVNURL/Delivery/scripts/unix/make_unix_layout
	</pre>		</pre>

Line 32:		Line 32:

	<pre>		<pre>
	svn export $SVNURL~~/trunk~~/Delivery/scripts/unix/make_debian_package		svn export $SVNURL/Delivery/scripts/unix/make_debian_package
	</pre>		</pre>

Line 53:		Line 53:

	<pre>		<pre>
	svn export $SVNURL~~/trunk~~/Delivery/scripts/unix/make_rpm_package		svn export $SVNURL/Delivery/scripts/unix/make_rpm_package
	</pre>		</pre>

Line 67:		Line 67:

	<pre>		<pre>
	svn export $SVNURL~~/trunk~~/Delivery/scripts/unix/make_svr_package		svn export $SVNURL/Delivery/scripts/unix/make_svr_package
	</pre>		</pre>

Arnofiva: Linux Packages moved to Unix/Linux Packages

2008-05-28T21:27:31Z

Linux Packages moved to Unix/Linux Packages

← Older revision		Revision as of 21:27, 28 May 2008
(No difference)

Arnofiva at 21:52, 16 May 2008

2008-05-16T21:52:37Z

← Older revision		Revision as of 21:52, 16 May 2008
Line 1:		Line 1:
	[[Category:Build Scripts]]		[[Category:Build Scripts]]

	For building binary installation packages for different Linux distribution you can use the scripts '''make_debian_package''' and '''~~make_rpm_package~~'''. This is a step by step manual on how to create such packages with these scripts. Since the source is the same for all distributions, the resulting packages are not distribution specific. This means you should be able to install e.g. a resulting .deb package on Debian and Ubuntu.		For building binary installation packages for different Linux/Unix distribution you can use the scripts '''make_debian_package''', '''make_rpm_package''' and '''make_svr_package'''.

			== Introduction ==

			This is a step by step manual on how to create such packages with these scripts. Since the source is the same for all distributions, the resulting packages are not distribution specific. This means you should be able to install e.g. a resulting .deb package on Debian and Ubuntu.
			In general the scripts take an existing EiffelStudio delivery, copy all files to a temporary Unix root directory and call the packaging tools for the specific distribution.

			Note that you should only create packages from deliveries built for your specific architecture. This is because the packaging tools automatically determine your architecture and store that information in the resulting package. So lets say you have an amd64 machine, only try to create packages for linux-x86-64 deliveries. The package will then be tagged for x86_64 architectures. Because the packaging tools automatically detect dynamic library dependencies, unfortunately it is not possible to create packages for other architectures, even if you use an already compiled delivery.

			Also if the Delivery includes a '''docs/''' directory, the packaging scripts will automatically create an architecture independent package only containing the documentary for EiffelStudio. This is to keep the size for the main package as little as possible.


	== Prerequisites ==		== Prerequisites ==

Arnofiva: /* Files in packaging/ */

2008-05-16T21:30:27Z

Files in packaging/

← Older revision		Revision as of 21:30, 16 May 2008
Line 146:		Line 146:
	* '''rpm/eiffelstudio.spec.sh''' and '''rpm/eiffelstudio-doc.spec.sh''' create RPM spec files which contain the same information file as the control for Debian packages. Except that when packaging it is easier if there are two separate files for the main and doc package. As a difference to Debian packages, the .spec files for RPM already include the install/remove scripts (Although simplified because user input through the console is not allowed with RPM during installation).		* '''rpm/eiffelstudio.spec.sh''' and '''rpm/eiffelstudio-doc.spec.sh''' create RPM spec files which contain the same information file as the control for Debian packages. Except that when packaging it is easier if there are two separate files for the main and doc package. As a difference to Debian packages, the .spec files for RPM already include the install/remove scripts (Although simplified because user input through the console is not allowed with RPM during installation).
	* '''rpm/RPMS''' is the directory in which '''rpmbuild''' will create the new packages.		* '''rpm/RPMS''' is the directory in which '''rpmbuild''' will create the new packages.
	* '''svr/pkginfo.sh'''/'''svr/pkginfo-doc.sh''' creates a pkginfo file containing general information for each package.		* '''svr/pkginfo.sh''' and '''svr/pkginfo-doc.sh''' creates a pkginfo file containing general information for each package.
	* '''svr/preremove.sh''' creates a the preremove scripts which gets called when uninstalling EiffelStudio (similar to Debian's '''prerm.sh''')		* '''svr/preremove.sh''' creates a the preremove scripts which gets called when uninstalling EiffelStudio (similar to Debian's '''prerm.sh''')
	* '''svr/reqeust.sh''' creates a script which is called before installing the resulting package. The scripts simply prints some information on how to generate the precompile libraries after the installation. The reason why we (currently) can not do this as convenient as for Debian/RPM is that the package manager for .svr packages clears all environment variables when calling these scripts.		* '''svr/reqeust.sh''' creates a script which is called before installing the resulting package. The scripts simply prints some information on how to generate the precompile libraries after the installation. The reason why we (currently) can not do this as convenient as for Debian/RPM is that the package manager for .svr packages clears all environment variables when calling these scripts.

Arnofiva: /* References */

2008-05-16T21:25:00Z

References

← Older revision		Revision as of 21:25, 16 May 2008
Line 194:		Line 194:
	* http://www.rpm.org/max-rpm/		* http://www.rpm.org/max-rpm/
	* http://pmc.ucsc.edu/~dmk/notes/RPMs/Creating_RPMs.html		* http://pmc.ucsc.edu/~dmk/notes/RPMs/Creating_RPMs.html

			UNIX:

			* http://docsrv.sco.com/SDK_tools/CTOC-PackagSWApps.html
			* http://www.cymru.com/Documents/UNIX/package.txt
			* http://dlc.sun.com/osol/docs/content/IPS/ggcph.html (Opensolaris)