Mailinglist Archive: opensuse-buildservice (189 mails)

< Previous Next >
Re: [opensuse-buildservice] inject local rpm data for buildinfo calculation
  • From: Marcus Hüwe <suse-tux@xxxxxx>
  • Date: Thu, 26 Feb 2009 13:16:49 +0100
  • Message-id: <20090226121649.GA3126@xxxxxxxxxxxxxxxxxxx>
On 2009-02-25 14:59:38 +0100, Michael Schroeder wrote:
How about using Build.pm's internal format?

I've tried that now but faced some "problems". If I understand it correctly
the format which is used by Build::readdeps() looks like this:
P:<id>: <list of provides separated by a whitespace>
R:<id>: <list of requires separated by a whitespace>
And <id> looks like <pkgname><some other info> - at least that's the impression
I got after reading the code + looking at e.g. createyastdeps.
So an example entry would look like this:

P:foo-bar-gui-qt: foo-bar-gui-qt = 1.0
R:foo-bar-gui-qt: libfoo
P:foo-bar-gui-gtk: foo-bar-gui-gtk = 1.0
R:foo-bar-gui-gtk: libbar

These are valid package names but aren't parsed correctly by Build::readdeps()
which is due to
...
if ($s =~ s/^P:(.*):$/$1/) {
my $pkgid = $s;
$s =~ s/-[^-]+-[^-]+-[^-]+$//;
$provides{$s} = \@ss;
...
# the same for provides

The problem is that I didn't get the idea of this substitute (apart from
causing problems). Additionally what's the idea of the $pkgidp hashref which
can be passed to Build::readdeps()?


Marcus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups