openembedded-core.git/meta/classes/package_rpm.bbclass, branch dizzy

package_rpm: Add optional improved directory handling

2014-09-03T09:24:29+00:00

During spec generation, ideally directories should not be auto
packaged under the %file section of rpm packages but take ownership of
specific directories.

* packages only empty directories or explict directory.
   See:
       - http://www.rpm.org/max-rpm/s1-rpm-inside-files-list-directives.html
       - "The %dir Directive"

* This will prevent the overlapping of security permission.
   For example, in Tizen the directory /etc have smack label 'System::Shared'
   So Only one package should own and set the label of /etc to prevent
   the overwriting of the smack label.

Existing behaviour is maintained if DIRFILES is not set. If it is set,
the modified behaviour is used. If can be set to an empty value by
core recipes to trigger the modified behaviour.

[RP: Modified to allow optional usage of DIRFILES]
Signed-off-by: Ronan Le Martret 
Signed-off-by: Richard Purdie

package_rpm: Add builddir macro to define source directory

2014-09-02T16:51:45+00:00

This allows its usage in other RPM macros so files in ${S} can be found.

Signed-off-by: Richard Purdie

package_rpm: Add custom extension support for spec generation.

2014-09-02T16:51:44+00:00

Add hooks to allow customisation of the rpm spec files. Since python functions
aren't visible in the data store, one variable is used to trigger the call to
a separately named function. A dummy function is not provided since this then
triggers various class ordering complexities which are best avoided.

Ultimately this will be replaced by a refactor of the code to generate the
spec file using a python class.

This allows the tizen layer to add hooks for the security manifests for
example.

Signed-off-by: Richard Purdie

package_rpm.bbclass: Should be using HOST_* not TARGET_*

2014-07-08T10:19:48+00:00

When building target packages, HOST_OS and TARGET_OS are the same, as is the
VENDOR field.  However, when building an SDK this is not true.  The patch
corrects the oversight and switches to using the 'HOST' version and resolves
the issue of meta-mingw not working w/ the rpm packaging.

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

classes/package_rpm.bbclass: Fix SDK Suffix reference

2014-06-25T10:49:39+00:00

The meta-mingw layer attempts to change the SDK Suffix, but the rpm
packaging had a hard coded reference to _nativesdk.

I did a quick scan for other hard coded entries and did not fine any
more.

Signed-off-by: Mark Hatle 
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_rpm.bbclass: archive the source to srpm package

2014-03-21T17:01:30+00:00

The archiver.bbclass will put the sources to ARCHIVER_OUTDIR according
to configuration, then the rpmbuild -bs will create the srpm.

[YOCTO #4986]
[YOCTO #5113]

Signed-off-by: Robert Yang

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