/ howto / package |
|
| Documentation |
|
Gambas must be packaged the way described in this document, because the development environment relies on this structure when it creates a package of a gambas project.
If a distribution does not follow this requirement, then the packages generated by the development environment won't be able to be installed, and the user will be very unhappy.
Not all distributions make correct gambas binary packages at the moment. So, if you are a packager from these distributions, and if you read this text, please try to help Gambas work on your distribution.
Thanks in advance,
Benoît.
The specifications look like the ones for Gambas 1.0, except that lib.XXX.component files were renamed as XXX.component, and that now a component can have a part written in Gambas.
Gambas binary packages must have the following names and contents:
This package includes the Gambas interpreter needed to run Gambas applications.
It contains:
![]() | Note that gb.la, gb.so, gb.so.0 and gb.so.0.0.0 do not need to be distributed. They are temporary files used for generating gb.info and gb.list only. |
Its name must be gambas2-runtime.
![]() | The gbr2 symbolic link MUST be in the PATH, otherwise executables will not work. |
This package includes all tools needed to compile Gambas projects without having to install the complete development environment.
It contains:
This package includes the scripter program that allows to write script files in Gambas.
It contains:
It depends on the following Gambas packages:
![]() | The gbs2 symbolic link MUST be in the PATH, otherwise scripts will not work. |
Each gambas component must have its own package.
The package of a component contains:
Then name of a component package MUST BE gambas2-gb-XXX where gb-XXX is the name of the component, the point being replaced by a minus sign.
For example, the gb.qt component package name is gambas2-gb-qt. It must include:
You must follow the previous rules for these components, except that there is no shared library files inside.
![]() | Note that gb.debug, gb.eval and gb.draw do not have their own package, as they are distributed with the gambas2-runtime package. |
This package includes the complete Gambas Development Environment, with the database manager, and the help files.
It contains:
Its name must be gambas2-ide.
![]() |
The IDE relies on the following external tools:
For example, on Mandriva, they are:
|
This package includes all the example projects provided with Gambas.
![]() |
When packaging the examples, be careful that a Gambas project includes some hidden files and directories.
These are:
|
It depends on the following Gambas packages:
This package includes the help files generated from the wiki located at http://gambasdoc.org.
They are installed in the $(INSTALL)/share/gambas2/help directory, where $(INSTALL) must be replaced by the Gambas installation directory.
The contents of that directory is the following:
This package depends on the gambas2-ide package.
Its name must be gambas2-help.
Gambas binary packages must follow the following names and contents:
This package includes the Gambas interpreter needed to run Gambas applications.
It contains:
This package must register the application/x-gambas mime type as specified by the application-x-gambas.xml file and the application-x-gambas.png icon.
Each component must have its own package.
The package of a component contains:
For example, the gb.qt.ext component package name is gambas-gb-qt-ext.