# We have our own implementation because:
# - our algorighm can do fewer tests so is faster
# - it saves testing to see if gdr is installed
+
+ # NB we use this jsut for deciding whether to run gdr make-patches
+ # Before reusing this algorithm for somthing else, its
+ # suitability should be reconsidered.
+
my $walk = $head;
local $Debian::Dgit::debugcmd_when_debuglevel = 3;
printdebug "branch_is_gdr $head...\n";
my $cdata = git_cat_file $walk, 'commit';
my ($hdrs,$msg) = $cdata =~ m{\n\n} ? ($`,$') : ($cdata,'');
if ($msg =~ m{^\[git-debrebase\ (
- anchor | pseudomerge | changelog |
- make-patches | merged-breakwater
+ anchor | changelog | make-patches |
+ merged-breakwater | pseudomerge
) [: ] }mx) {
# no need to analyse this - it's sufficient
# (gdr classifications: Anchor, MergedBreakwaters)
sub cmd_build {
build_prep_early();
$buildproductsdir eq '..' or print STDERR <<END;
-$us: warning: build-products-dir set, but not supported by dgit build
-$us: warning: things may go wrong or files may go to the wrong place
+$us: warning: build-products-dir set, but not supported by dpkg-buildpackage
+$us: warning: build-products-dir will be ignored; files will go to ..
END
+ $buildproductsdir = '..';
my @dbp = (@dpkgbuildpackage, qw(-us -uc), changesopts_initial(), @ARGV);
my $wantsrc = massage_dbp_args \@dbp;
build_prep($wantsrc);