How to setup a FPC and Lazarus Ubuntu repository/pt

O que é um repositório?

Um repositório Ubuntu é um diretório. Ele pode ser guardado num disco local ou em um servidor Web ou FTP. To use it, you add its path into your /etc/apt/sources.list and setup a pgp key. Then you can simply install lazarus with your favourite package gui (e.g. synaptic) and fpc, fpc-src and lazarus will be downloaded, installed and updated automatically.

Who needs it?

Administrators who wants to install FPC+Lazarus on a pool of computers. Like in school. Or newbies who just want to quickly test it.

The directory structure

Let's assume you want create a repository available via the apache webserver. Then you need to setup a directory like /var/www/lazarus that is public readable and only writable by root.

Create a sub directory for each target you want to support:

 mkdir -p /var/www/lazarus/dists/lazarus-testing/universe/binary-i386
 mkdir -p /var/www/lazarus/dists/lazarus-testing/universe/binary-amd64

The debs

Put the fpc, fpc-src and lazarus deb files into it.

Creating the deb files yourself

You can create the debs with the scripts in tools/install/ of the lazarus sources.

Install development packages

• install development packages:

 sudo apt-get install libgtk2.0-dev libgtk1.2-dev libgdk-pixbuf-dev libgpmg1-dev fakeroot libncurses5-dev

• Install the latest stable FPC. This is needed to build the new FPC and Lazarus:

 Either the deb files from the official site or the tar.gz.

• Download the FPC sources. To get the current development version you can use the command below. To get a more stable version, see Installing_Lazarus#FPC Sources:

 svn co http://svn.freepascal.org/svn/fpc/trunk fpc

• Download the lazarus sources:

 svn co http://svn.freepascal.org/svn/lazarus/trunk lazarus

Build new deb

• go into the lazarus install script directory:

 cd lazarus/tools/install

• build the fpc deb. The following script will build a single fpc deb using the date as version. As parameter you must specify the path of the FPC sources you downloaded above:

 sudo ./create_fpc_deb.sh fpc /path/to/the/sources/of/fpc/

• install the new fpc deb. This is needed to build the lazarus deb, which depends on the new fpc deb. Don't forget to uninstall first your old FPC.

 sudo dpkg -i fpc_2.3.1-070726_i386.deb

• build the fpc-src deb. This works pretty much the same as above:

 ./create_fpc_deb.sh fpc-src /path/to/the/sources/of/fpc/

• build the lazarus deb. You can either build a normal lazarus:

 ./create_lazarus_deb.sh append-revision

or a lazarus using gtk2:

 ./create_lazarus_deb.sh gtk2 append-revision

Replace the deb files in the repository

• Now you have 3 deb files. Copy them to your repository:

 cp fpc_2.3.1-070726_i386.deb fpc-src_2.3.1-070726_i386.deb lazarus_0.9.23.11636-0_i386.deb \
   /var/www/lazarus/dists/lazarus-testing/universe/binary-i386/

• Don't forget to remove the old ones.

PGP Key

You need to sign the debs with a PGP key, so that the target systems can be sure, that no evil-doer replaced the files.

Creating a PGP key

You can use tools like seahorse or thunderbird to create the PGP key.

• Install seahorse
• start seahorse
• Key > Create new key
• A window popup up asking for the type. Choose PGP Key.
• Give a full name and an email adress and click Create.
• The passphrase is needed to encrypt the created files. This way no one can use the keys but you, even if they manage to steal your files. If you think, your files will never stolen or read by others you can leave them empty.
• Creating the keys will take some minutes

Upload the key to a public key server

In order to share the key you can upload the key to a public key server.

• start seahorse
• Edit > Preferences > Key servers > Publish key to: choose a key server. For example: hkp://pgp.mit.edu:11371. Close the dialog.
• Remote > Sync and publish key > Sync.

Remember the key ID

You need the key ID later. The key ID is shown in seahorse. But you can see it also via:

 gpg --list-keys

Updating repository files

Put the following script into /var/www/lazarus, edit it for your needs and run it:

#!/usr/bin/env bash

set -x

GPGHome=/home/gaertner/.gnupg/
MainDir=dists/lazarus-testing

for Arch in i386 amd64; do
  Dir=$MainDir/universe/binary-$Arch

# create index
apt-ftparchive packages $Dir > $Dir/Packages
cat $Dir/Packages | gzip -9c > $Dir/Packages.gz
cat $Dir/Packages | bzip2 > $Dir/Packages.bz2

done

# create Release file
rm -f $MainDir/Release*
Date=`date`
echo "Origin: Lazarus" >> $MainDir/Release
echo "Label: Lazarus" >> $MainDir/Release
echo "Suite: unstable" >> $MainDir/Release
echo "Codename: lazarus-testing" >> $MainDir/Release
echo "Version: 1.0" >> $MainDir/Release
echo "Date: $Date" >> $MainDir/Release
echo "Architectures: amd64 i386" >> $MainDir/Release
echo "Components: universe" >> $MainDir/Release
echo "Description: Lazarus testing 1.0" >> $MainDir/Release

apt-ftparchive release $MainDir >> $MainDir/Release

# sign Release file
gpg --sign --homedir=$GPGHome -ba -o $MainDir/Release.gpg $MainDir/Release

# end.

This will create index files Packages, Packages.bz2 and Packages.gz. And it will create the Release file containing the checksums of the deb packages and sign it (Release.gpg).

Adding the repository to a client

The following steps must be done on each computer, you want to use your repository.

Add the key

Download the key from the public key server:

 gpg --keyserver hkp://pgp.mit.edu:11371 --recv-keys 3A5B1204

The 3A5B1204 should be replaced with your key id. Check the output, that you got the right key.

Add it to the apt system:

 gpg --export 3A5B1204 | sudo apt-key add -

You can see the list of apt keys with:

 sudo apt-key list

Add the repository

You can use synaptic for this or edit the /etc/apt/sources.list directly. Add the line:

 deb http://progprak.scale.uni-koeln.de/lazarus/ lazarus-testing universe

Replace the http path with your own.

Install Lazarus

For example:

 sudo apt-get update
 sudo apt-get install lazarus

From the Free Pascal wiki, page "How to setup a FPC and Lazarus Ubuntu repository/pt", as it stood on 2007-10-19 after a change by Antoniog, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's Licensing page. If you have concerns about this material, message the admin.