openembedded-core.git/meta/classes/package_ipk.bbclass, branch fido

packaging: allow globs in CONFFILES

2015-02-19T07:50:44+00:00

Allow globs in CONFFILES.

This patch changes the way of CONFFILES handling. After this  change,
the CONFFILES can take the same form as FILES. That means, we don't
have to list a bunch of files for CONFFILES. It will just be expanded
like the FILES variable.

We don't assume default value for CONFFILES in OE. But distro vendors could
provide a default value for CONFFILES in their distro configuration file
like below.

    CONFFILES = "${sysconfdir}"

In this way, files under /etc are treated as configuration files by
default. Of course, setting CONFFILES in recipes take precedence over
the CONFFILES. For example, if the recipe author decides that package A
should only treat files under ${sysconfdir}/default/ as config files,
he/she can write like this.

    CONFFILES_A = "${sysconfdir}/default"

[YOCTO #5200]

Signed-off-by: Chen Qi 
Signed-off-by: Richard Purdie

package_ipk.bbclass: Fix SRC_URI whitespace handling

2014-10-06T15:03:03+00:00

The SRC_URI may contain whitespace, but be otherwise empty.  This can happen
in the case:

MYSRC = ""
MYSRC_arm = "file://myarm.patch"
SRC_URI += "${MYSRC}"

Unless we strip blank spaces, to determine if it is empty, we can end up
generating a "Source: " line which in invalid.  This leads to the error:

  invalid Source: field is speified in the generated CONTROL file

Signed-off-by: Mark Hatle 
Signed-off-by: Richard Purdie

package_ipk.bbclass: Support hierarchical feed

2014-06-17T07:56:11+00:00

This patch allows for an optional new layout for ipk feed directories which I've
called a 'hierarchical feed' and is based on how Debian pools package files. It
is disabled by default and is enabled by setting IPK_HIERARCHICAL_FEED to "1".

In the traditional feed layout, package files are placed in //.
This can lead to several thousand files existing in a single directory which is
often a problem if developers want to upload a package feed to a shared web
hosting provider. For example, in my case, listing files via FTP only shows the
first 2000 files, breaking my scripts which attempt to upload only new and
changed files via FTP.

In the hierarchical feed, package files are written to
///, where pkg_prefix is the first letter
of the package file name for non-lib packages or "lib" plus the 4th letter of
the package file name for lib packages (eg, 'l' for less, 'libc' for libc6).
pkg_subdir is the root of the package file name, discarding the version and
architecture parts and the common suffixes '-dbg', '-dev', '-doc', '-staticdev',
'-locale' and '-locale-*' which are listed in meta/conf/bitbake.conf.

This change relies on recent patches to opkg-utils which support hierarchical
package feeds.

Signed-off-by: Paul Barker 
Signed-off-by: Richard Purdie

package_*.bbclass: Simplify addtask

2014-03-28T13:42:56+00:00

The package_write task was previously removed. Remove a remaining superfluous
reference to it.

Signed-off-by: Richard Purdie

package: Drop do_package_write task

2014-02-24T16:18:57+00:00

The reasons this task was introduced are lost in the mists of time. It
allowed for the a single "package_write" task instead of spelling out
the explicit package backends, however in all but one case we do that
anyway.

As such as might as well give in and delete the task, converting that
single reference into explicit dependencies.

This gives bitbake a bit less work to to when processing the runqueue
since there are less tasks (but more dependencies in some cases).

Signed-off-by: Richard Purdie

package_*.bbclass: remove references to the old bash indexing routines

2014-02-14T12:25:14+00:00

Package indexing is done in python and package-index.bb uses the new
routines.

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

conf/bitbake.conf: default HOMEPAGE to blank instead of unknown

2014-02-11T11:56:35+00:00

The default value for HOMEPAGE of "unknown" has been in place since the
early OE-Classic days, but it doesn't really make sense - "unknown" is
not a valid URL and it just means we have to explicitly check for this
hardcoded string if we're displaying the value in some form of UI, such
as Toaster.

This has required some changes to the packaging classes as they
previously did not expect the value to be blank.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

Cleanup image,rootfs_ipk,package_ipk bbclass files

2014-02-11T11:50:26+00:00

This commit cleans up the functions that were ported to python.

Signed-off-by: Laurentiu Palcu

package_(deb|ipk).bbclass: remove the stamp when creating package from cache

2014-02-11T11:50:25+00:00

If the packages are created from cache, we need to remove the stamp so
that we re-generate the index files at do_rootfs time.

Signed-off-by: Laurentiu Palcu

package_{ipk, deb, rpm}.bbclass: support additional user-defined metadata

2014-01-28T00:48:24+00:00

Additional metadata from user-defined variable is written into
control/spec file of binary package.

Three variables are searched for adiitional package metadata:

  * PACKAGE_ADD_METADATA__
  * PACKAGE_ADD_METADATA_
  * PACKAGE_ADD_METADATA

First found variable with defined value wins.

 is a package name.  is a distinct name of specific
package type:

  * IPK for .ipk packages
  * DEB for .deb packages
  * RPM for .rpm packages

Variable can contain multiple [one-line] metadata fields separated by
literal sequence '\n'. Separator can be redefined through variable flag
'separator'. In package control/spec file separator is replaced by
newline character.

Signed-off-by: Leonid Borisenko 
Signed-off-by: Martin Jansa 
Signed-off-by: Saul Wold