Fppkg field test with fpc release 2.2.4
The fpc-release after the 2.2.x releases will be based partly on the new fppkg package system. The basics of this package system are already available in fpc version 2.2.4 so we can test the system in reality.
At first only one package is available for installation but more will follow. We also want to test if it is possible to release updates of packages which are part of fpc itself. So when there is a usefull update for one of the packages we can use this system to release an update for only this package, without having to release a full new version of the compiler.
The new package system is not yet fully documented and any help is appreciated. This document is just a first introduction to get started and collect knowledge about any problems we may find during this test.
How to use fppkg
When fpc 2.2.4 is installed the 'fppkg' program will also be installed. You can get a list of all installed packages and those packages which are available using the command
fppkg list
This will list all fpc packages which are already installed with their version and all available packages which are not installed yet. The version number of the fpc-packages will be equal to the fpc-release they belong to, with a suffix which indicates the release. A suffix of '-0' indicates that it's a pre-release, for example a release candidate. A suffix of '-1' indicates that it is the version which was released together with the official compiler-release. A version of '2.2.4-1' for example indicates that the installed package is the package which came with the initial fpc 2.2.4 release.
Other packages which are not part of a fpc-release can follow their own version-numbering. At the moment of writing of this article, there is only one such package available, namely 'lNet'
Install a package
The following command will install the lNet package
fppkg install lnet
When the current user has rights to install the package in the global (system-wide) directory the package will be installed there. Else the package will be installed at a user-specific location. In fact the package-zip containing the sources is downloaded and extracted. Then the package is build and installed. For more information about the exact process check the article about fpmake.
After installation the units in the packages are available for use. (Note that when you haven't installed the package in a system-wide location, you may have to add the user-specific location to your compiler configuration)
Update package list
When you want to check if there are any new packages available, you have to perform a
fppkg update
command to update the local copy of the 'database' with available packages. After a update 'fppkg list' will show the latest packages.