This is the forth alpha for the upcoming 2.4.x releases. This release
introduces two features as well as bug fixes and translation updates.
The first feature which is added in this release is an API addition for
use in buildfarm. With a new method, it is now possible to determine
the old packages that will be used to create delta packages from.
"Build flags" is another feature introduced in this release. Build flags
can be used to enable/disable some operations/packages at build time.
Currently, two flags are accepted: noDebug and noDelta.
Changes since 2.4_alpha3
------------------------
fatih (11):
build: Reload actions script for each build type
installdb: Parse directory names correctly
l10n: Update messages
build: Do not allow duplicate path values in spec file
build: Fail if a path does not start with a slash
build: Add a method to determine delta packages to be created
l10n: Update messages
index: Ignore debug packages of obsoleted packages
build,specfile: Implement support for build flags
dtd,rng: Accept BuildFlags tag inside Package tags
l10n: Update Turkish translations
igungor (1):
l10n: Revert the latest Italian translation which breaks pisi.
transifex (5):
l10n: Updated Italian (it) translation to 81% (Hudaverdi Sarialtin)
l10n: Updated French (fr) translation to 100% (Philippe Svetoslavsky)
l10n: Updated Dutch (Flemish) (nl) translation to 100% (Antoon Tolboom)
l10n: Updated Dutch (Flemish) (nl) translation to 100% (Antoon Tolboom)
l10n: Updated French (fr) translation to 100% (Philippe Svetoslavsky)
Currently, it supports two flags: noDebug, noDelta.
The usage is simple:
<Package>
...
<BuildFlags>
<Flag>noDebug</Flag>
<Flag>noDelta</Flag>
</BuildFlags>
...
</Package>
noDebug flag is used to disable building of a debug package for this
package tag.
noDelta flag is used to disable building of delta packages
automatically. It doesn't change the behaviour of "pisi delta" command.
This will be used by buildfarm. It accepts release numbers to create
delta packages for stable distribution releases. If the release number
is not given, it searches the binary package dirs for old packages and
creates delta packages. max_count can be specified to limit numbers of
delta packages.
It is possible to override search paths via search_paths parameter.
release and max_count parameters cannot be used at the same time.
This commit also removes the max_delta_count option from config file
since it is useless and confusing.
This is the third alpha for the upcoming 2.4.x releases. This release
introduces a new feature for building source packages with different
configurations using the same actions.py. This is achieved with
BuildType tags specified between Package tags.
It is also possible to write build dependencies inside Package tags with
this release. This is needed since additional build dependencies could
be needed for different build types.
Changes since 2.4_alpha2
------------------------
fatih (12):
build: Minor simplifications
build: More simplifications
build: Cosmetic change
build: Check build dependencies for unpack too
sourcearchive: Pass target dirs to unpack methods
specfile: Accept BuildType tag inside Package tags
build: Add support for build types
build: Colorize unpack message
specfile: Accept BuildDependencies inside Package tags
build: Iterate over Package tags to gather all build deps
build: Remove redundant check in previous commit
build,config: Add a new config option to ignore build types
ozan.caglayan (1):
actionsapi/kerneltools: Don't fail if listnewconfig is not available
transifex (4):
l10n: Updated Polish (pl) translation to 46% (Michał Komasa)
l10n: Updated Polish (pl) translation to 47% (Michał Komasa)
l10n: add uk (Коростіль Данило)
l10n: Updated Italian (it) translation to 81% (Ali Işıngör)
With build types, it is possible to use the same actions.py
for re-building the package with different options. In actions.py
scripts, get.buildTYPE() function can be used to get the current
build type.
A BuildType tag must be specified inside the Package tag of the related
binary package.