On Friday 23 July 2010 04:57:26 brook.hong@nokia.com wrote:
Thanks Pavol. I mean the command "rpmbuild -ba somepackage.spec". Either webui or osc passes a -debug option to the build script, which generates relevant macros for rpmbuild. Then rpmbuild generates those debuginfo and debugsource packages.
Adrian, the aggregatepac operation does copy the debuginfo and debugsource packages to target, here I added one line to skip them when nosources flag is set.
okay, I have submitted a slightly different version with an exact match for rpm packages. I dunno how debian is handling debug packages at all. Does anyone know how we can detect debug packages on debian ? thanks adrian
diff --git a/src/backend/bs_sched b/src/backend/bs_sched index 5ef13bb..8392049 100755 --- a/src/backend/bs_sched +++ b/src/backend/bs_sched @@ -2906,6 +2906,7 @@ sub rebuildaggregate { next unless $r->{'source'}; next if $abinfilter && !$abinfilter->{$r->{'name'}}; next if $jobbins{$r->{'name'}};
next if ($copysources == 0) && ($r->{'name'} =~ /-debug(info|source)/); $jobbins{$r->{'name'}} = 1; my $basename = $abin; $basename =~ s/.*\///;
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org