diff options
| -rw-r--r-- | .foo | 0 | ||||
| -rw-r--r-- | BUGS | 0 | ||||
| -rw-r--r-- | PROGRAMMING | 187 | ||||
| -rw-r--r-- | README | 100 | ||||
| -rw-r--r-- | Test.pm | 254 | ||||
| -rwxr-xr-x | dh_getopt.pl | 57 | ||||
| -rw-r--r-- | dh_installmime.1 | 38 | ||||
| -rw-r--r-- | dh_installmodules.1 | 35 | ||||
| -rw-r--r-- | dh_installpam.1 | 30 | ||||
| -rwxr-xr-x | dh_installxaw | 65 | ||||
| -rw-r--r-- | dh_installxaw.1 | 40 | ||||
| -rwxr-xr-x | dh_listpackages | 8 | ||||
| -rw-r--r-- | dh_listpackages.1 | 25 | ||||
| -rw-r--r-- | dh_perl.1 | 60 | ||||
| -rw-r--r-- | dh_testversion.in | 23 | ||||
| -rw-r--r-- | foo | 2 | ||||
| -rw-r--r-- | from-debstd | 63 | ||||
| -rw-r--r-- | me | 0 | ||||
| -rw-r--r-- | pgptemp.$00 | 0 |
19 files changed, 0 insertions, 987 deletions
diff --git a/PROGRAMMING b/PROGRAMMING deleted file mode 100644 index 7dc0c638..00000000 --- a/PROGRAMMING +++ /dev/null @@ -1,187 +0,0 @@ -This file documents things you should know to write a new debhelper program. - -Standardization: ---------------- - -There are lots of debhelper commands. To make the learning curve shallower, -I want them all to behave in a standard manner: - -All debhelper programs have names beginning with "dh_". This is so we don't -pollute the name space too much. - -Debhelper programs should never output anything to standard output except -error messages, important warnings, and the actual commands they run that -modify files under debian/ and debian/tmp, etc (this last only if they are -passed -v, and if you output the commands, you should indent them with 1 tab). -This is so we don't have a lot of noise output when all the debhelper commands -in a debian/rules are run, so the important stuff is clearly visible. - -Debhelper programs should accept the options, -v, -i, -a, -p, --no-act, and --P, and any long forms of these options, like --verbose . If necessary, the -options may be ignored. - -If debhelper commands need config files, they should use -debian/package.filename as the name of the config file (replace filename -with whatever your command wants), and debian/filename should also be -checked for config information for the first binary package in -debian/control. Also, debhelper commands should accept the same sort of -information that appears in the config files, on their command lines, if -possible, and apply that information to the first package they act on. - -Debhelper programs should never modify the debian/postinst, debian/prerm, -etc scripts, instead, they can add lines to debian/postinst.debhelper, etc. -The autoscript() function (see below) is one easy way to do this. -dh_installdeb is an exception, it will run after the other commands and -merge these modifications into the actual postinst scripts. - -There are always exceptions. Just ask me. - -Introducing dh_lib: ------------------- - -All debhelper programs use the dh_lib library (actually it's a shell script) -to parse their arguments and set some useful variables. It's not mandatory -that your program use dh_lib, but it will make it a lot easier to keep it in -sync with the rest of debhelper if it does, so this is highly encouraged. - -Typically, you invoke dh_lib like this: - -PATH=debian:$PATH:/usr/lib/debhelper -. dh_lib - -The path statement is there to make your program look first in debian/ for -dh_lib (so users can install a modified version there if necessary), then the -rest of the path, then the canonical location of dh_lib, /usr/lib/debhelper. - -Argument processing: -------------------- - -All debhelper programs should respond to certain arguments, such as -v, -i, --a, and -p. To help you make this work right, dh_lib handles argument -processing. - -As soon as dh_lib loads, it processes any arguments that have been passed to -your program. The following variables may be set during this stage; your -program can use them later: - -switch variable description --v DH_VERBOSE should the program verbosely output what it is - doing? ---no-act DH_NO_ACT should the program not actually do anything? --i,-a,-p DH_DOPACKAGES a space delimited list of the binary packages - to act on --i,-p DH_DOINDEP a space delimited list of the binary independent - packages to act on --a,-p DH_DOARCH a space delimited list of the binary dependent - packages to act on --n DH_NOSCRIPTS if set, do not make any modifications to the - package's postinst, postrm, etc scripts. --X DH_EXCLUDE exclude a something from processing (you - decide what this means for your program) - DH_EXCLUDE_GREP same as DH_EXCLUDE, except all items are - separated by '|' characters, instead of spaces, - handy for egrep -v --x DH_INCLUDE_CONFFILES - include conffiles. It's -x for obscure - historical reasons. --d DH_D_FLAG you decide what this means to your program --r DH_R_FLAG you decide what this means to your program --k DH_K_FLAG you decide what this means to your program --P DH_TMPDIR package build directory (implies only one - package is being acted on) --u DH_U_PARAMS will be set to a string, that is typically - parameters your program passes on to some - other program. --m DH_M_PARAMS will be set to a string, you decide what it - means to your program --V DH_V_FLAG will be set to a string, you decide what it - means to your program --V DH_V_FLAG_SET will be 1 if -V was specified, even if no - parameters were passed along with the -V --A DH_PARAMS_ALL generally means that additional command line - parameters passed to the program (other than - those processed here), will apply to all - binary packages the program acts on, not just - the first ---init-script DH_INIT_SCRIPT will be set to a string, which specifies an - init script name (probably only - dh_installinit will ever use this) - -Any additional command line parameters that do not start with "-" will be -ignored, and you can access them later just as you normally would ($1, $2, -etc). - -If you need a new command line option, just ask me, and I will add it. - -Global variables: ----------------- - -The following variables are also set, you can use any of them: - -MAINPACKAGE the name of the first binary package listed in - debian/control -DH_FIRSTPACKAGE the first package we were instructed to act on. This package - typically gets special treatment, additional arguments - specified on the command line may effect it. - -Functions: ---------- - -Dh_lib also contains a number of functions you may find useful. - -doit() - Pass this function a string that is a shell command. It will run the - command (unless DH_NO_ACT is set), and if DH_VERBOSE is set, it will - also output the command to stdout. You should use this function for - almost all commands your program performs that manipulate files in - the package build directories. -complex_doit() - This is the same as doit(), except you can pass more complicated - commands to it (ie, commands involving piping redirection) -verbose_echo() - Pass this command a string, and it will echo it if DH_VERBOSE is set. -error() - Pass this command a string, it will output it to standard error and - exit. -warning() - Pass this command a string, and it will output it to standard error - as a warning message. -tmpdir() - Pass this command the name of a binary package, it will return the - name of the tmp directory that will be used as this package's - package build directory. Typically, this will be "debian/tmp" or - "debian/package". -pkgfile() - Pass this command the name of a binary package, and the base name of a - file, and it will return the actual filename to use. This is used - for allowing debhelper programs to have configuration files in the - debian/ directory, so there can be one config file per binary - package. The convention is that the files are named - debian/package.filename, and debian/filename is also allowable for - the MAINPACKAGE. If the file does not exist, nothing is returned. -pkgext() - Pass this command the name of a binary package, and it will return - the name to prefix to files in debian/ for this package. For the - MAINPACKAGE, it returns nothing (there is no prefix), for the other - packages, it returns "package.". -isnative() - Pass this command the name of a package, it returns 1 if the package - is a native debian package. - As a side effect, VERSION is set to the version number of the - package. -autoscript() - Pass 3 parameters: - 1: script to add to - 2: filename of snippet - 3: sed commands to run on the snippet. Ie, s/#PACKAGE#/$PACKAGE/ - (optional) - This command automatically adds shell script snippets to a debian - maintainer script (like the postinst or prerm). - -Notes: ------ - -Dh_lib is still evolving. -There will probably be a perl version too, in the future. - --- Joey Hess <joeyh@master.debian.org> diff --git a/README b/README deleted file mode 100644 index 986eb02c..00000000 --- a/README +++ /dev/null @@ -1,100 +0,0 @@ -Debhelper is a collection of programs that can be used in debian/rules files -to automate common tasks. For further documentation, see the man pages for -dh_* commands. - -To help you get started, I've included examples of debian/rules files -that use debhelper commands extensively. See /usr/doc/debhelper/examples/ . -These files are also useful as they give one good order you can run the -various debhelper scripts in (though other variations are possible). - -Starting a new package: ----------------------- - -You can just use the example rules files and do the rest of the new package -set up by hand, or you could try the new dh-make package, which contains a -"dh_make" command that is similar to debmake, and tries to automate the -process. - -Converting from debstd to debhelper: ------------------------------------ - -See the file "from-debstd" for documentation on how to do this. - -Automatic generation of debian install scripts: ----------------------------------------------- - -Some debhelper commands will automatically generate parts of debian install -scripts. If you want these automatically generated things included in your -debian install scripts, then you need to add "#DEBHELPER#" to your scripts, -in the place the code should be added. "#DEBHELPER#" will be replaced by any -auto-generated code when you run dh_installdeb. - -All scripts that automatically generate code in this way let it be disabled -by the -n parameter. - -Note that it will be shell code, so you cannot directly use it in a perl -script. If you would like to embed it into a perl script, here is one way to -do that: - -print << `EOF` -#DEBHELPER# -EOF - - -Notes on multiple binary packages: ---------------------------------- - -If your source package generates more than one binary package, debhelper -programs will default to acting on all binary packages when run. If your -source package happens to generate one architecture dependent package, and -another architecture independent package, this is not the correct behavior, -because you need to generate the architecture dependent packages in the -binary-arch debian/rules target, and the architecture independent packages -in the binary-indep debian/rules target. - -To facilitate this, as well as give you more control over which packages -are acted on by debhelper programs, all debhelper programs accept the -following parameters: - --a Act on architecture dependent packages --i Act on architecture independent packages --ppackage Act on the package named "package" (may be repeated multiple - times) - -These parameters are cumulative. If none are given, the tools default to -affecting all packages. - -See examples/rules.multi for an example of how to use this. - -Package build directories -- debian/tmp, etc: --------------------------------------------- - -By default, all debhelper programs assume that the temporary directory used -for assembling the tree of files in a package is debian/tmp for the first -package listed in debian/control, and debian/<packagename> for each -additional package. - -Sometimes, you might want to use some other temporary directory. This is -supported by the -P flag. The directory to use is specified after -P, for -example, "dh_installdocs -Pdebian/tmp", will use debian/tmp as the temporary -directory. Note that if you use -P, the debhelper programs can only be -acting on a single package at a time. So if you have a package that builds -many binary packages, you will need to use the -p flag to specify which -binary package the debhelper program will act on. For example: - - dh_installdocs -pfoolib1 -Pdebian/tmp-foolib1 - dh_installdocs -pfoolib1-dev -Pdebian/tmp-foolib1-dev - dh_installdocs -pfoolib-bin -Pdebian/tmp-foolib-bin - -This uses debian/tmp-<package> as the package build directory. - -Other notes: ------------ - -* In general, if any debhelper program needs a directory to exist under - debian/, it will create it. I haven't bothered to document this in all the - man pages, but for example, dh_installdeb knows to make debian/tmp/DEBIAN/ - before trying to put files there, dh_installmenu knows you need a - debian/tmp/usr/lib/menu/ before installing the menu files, etc. - --- Joey Hess <joeyh@master.debian.org> diff --git a/Test.pm b/Test.pm deleted file mode 100644 index 55f80ac2..00000000 --- a/Test.pm +++ /dev/null @@ -1,254 +0,0 @@ -use strict; -package Test; -use Test::Harness 1.1501 (); -use Carp; -use vars (qw($VERSION @ISA @EXPORT @EXPORT_OK $ntest $TestLevel), #public-ish - qw($TESTOUT $ONFAIL %todo %history $planned @FAILDETAIL)); #private-ish -$VERSION = '1.13'; -require Exporter; -@ISA=('Exporter'); -@EXPORT=qw(&plan &ok &skip); -@EXPORT_OK=qw($ntest $TESTOUT); - -$TestLevel = 0; # how many extra stack frames to skip -$|=1; -#$^W=1; ? -$ntest=1; -$TESTOUT = *STDOUT{IO}; - -# Use of this variable is strongly discouraged. It is set mainly to -# help test coverage analyzers know which test is running. -$ENV{REGRESSION_TEST} = $0; - -sub plan { - croak "Test::plan(%args): odd number of arguments" if @_ & 1; - croak "Test::plan(): should not be called more than once" if $planned; - my $max=0; - for (my $x=0; $x < @_; $x+=2) { - my ($k,$v) = @_[$x,$x+1]; - if ($k =~ /^test(s)?$/) { $max = $v; } - elsif ($k eq 'todo' or - $k eq 'failok') { for (@$v) { $todo{$_}=1; }; } - elsif ($k eq 'onfail') { - ref $v eq 'CODE' or croak "Test::plan(onfail => $v): must be CODE"; - $ONFAIL = $v; - } - else { carp "Test::plan(): skipping unrecognized directive '$k'" } - } - my @todo = sort { $a <=> $b } keys %todo; - if (@todo) { - print $TESTOUT "1..$max todo ".join(' ', @todo).";\n"; - } else { - print $TESTOUT "1..$max\n"; - } - ++$planned; -} - -sub to_value { - my ($v) = @_; - (ref $v or '') eq 'CODE' ? $v->() : $v; -} - -sub ok ($;$$) { - croak "ok: plan before you test!" if !$planned; - my ($pkg,$file,$line) = caller($TestLevel); - my $repetition = ++$history{"$file:$line"}; - my $context = ("$file at line $line". - ($repetition > 1 ? " fail \#$repetition" : '')); - my $ok=0; - my $result = to_value(shift); - my ($expected,$diag); - if (@_ == 0) { - $ok = $result; - } else { - $expected = to_value(shift); - my ($regex,$ignore); - if (!defined $expected) { - $ok = !defined $result; - } elsif (!defined $result) { - $ok = 0; - } elsif ((ref($expected)||'') eq 'Regexp') { - $ok = $result =~ /$expected/; - } elsif (($regex) = ($expected =~ m,^ / (.+) / $,sx) or - ($ignore, $regex) = ($expected =~ m,^ m([^\w\s]) (.+) \1 $,sx)) { - $ok = $result =~ /$regex/; - } else { - $ok = $result eq $expected; - } - } - my $todo = $todo{$ntest}; - if ($todo and $ok) { - $context .= ' TODO?!' if $todo; - print $TESTOUT "ok $ntest # ($context)\n"; - } else { - print $TESTOUT "not " if !$ok; - print $TESTOUT "ok $ntest\n"; - - if (!$ok) { - my $detail = { 'repetition' => $repetition, 'package' => $pkg, - 'result' => $result, 'todo' => $todo }; - $$detail{expected} = $expected if defined $expected; - $diag = $$detail{diagnostic} = to_value(shift) if @_; - $context .= ' *TODO*' if $todo; - if (!defined $expected) { - if (!$diag) { - print $TESTOUT "# Failed test $ntest in $context\n"; - } else { - print $TESTOUT "# Failed test $ntest in $context: $diag\n"; - } - } else { - my $prefix = "Test $ntest"; - print $TESTOUT "# $prefix got: ". - (defined $result? "'$result'":'<UNDEF>')." ($context)\n"; - $prefix = ' ' x (length($prefix) - 5); - if ((ref($expected)||'') eq 'Regexp') { - $expected = 'qr/'.$expected.'/' - } else { - $expected = "'$expected'"; - } - if (!$diag) { - print $TESTOUT "# $prefix Expected: $expected\n"; - } else { - print $TESTOUT "# $prefix Expected: $expected ($diag)\n"; - } - } - push @FAILDETAIL, $detail; - } - } - ++ $ntest; - $ok; -} - -sub skip ($$;$$) { - my $whyskip = to_value(shift); - if ($whyskip) { - $whyskip = 'skip' if $whyskip =~ m/^\d+$/; - print $TESTOUT "ok $ntest # $whyskip\n"; - ++ $ntest; - 1; - } else { - local($TestLevel) = $TestLevel+1; #ignore this stack frame - &ok; - } -} - -END { - $ONFAIL->(\@FAILDETAIL) if @FAILDETAIL && $ONFAIL; -} - -1; -__END__ - -=head1 NAME - - Test - provides a simple framework for writing test scripts - -=head1 SYNOPSIS - - use strict; - use Test; - - # use a BEGIN block so we print our plan before MyModule is loaded - BEGIN { plan tests => 14, todo => [3,4] } - - # load your module... - use MyModule; - - ok(0); # failure - ok(1); # success - - ok(0); # ok, expected failure (see todo list, above) - ok(1); # surprise success! - - ok(0,1); # failure: '0' ne '1' - ok('broke','fixed'); # failure: 'broke' ne 'fixed' - ok('fixed','fixed'); # success: 'fixed' eq 'fixed' - ok('fixed',qr/x/); # success: 'fixed' =~ qr/x/ - - ok(sub { 1+1 }, 2); # success: '2' eq '2' - ok(sub { 1+1 }, 3); # failure: '2' ne '3' - ok(0, int(rand(2)); # (just kidding :-) - - my @list = (0,0); - ok @list, 3, "\@list=".join(',',@list); #extra diagnostics - ok 'segmentation fault', '/(?i)success/'; #regex match - - skip($feature_is_missing, ...); #do platform specific test - -=head1 DESCRIPTION - -L<Test::Harness> expects to see particular output when it executes -tests. This module aims to make writing proper test scripts just a -little bit easier (and less error prone :-). - -=head1 TEST TYPES - -=over 4 - -=item * NORMAL TESTS - -These tests are expected to succeed. If they don't something's -screwed up! - -=item * SKIPPED TESTS - -Skip is for tests that might or might not be possible to run depending -on the availability of platform specific features. The first argument -should evaluate to true (think "yes, please skip") if the required -feature is not available. After the first argument, skip works -exactly the same way as do normal tests. - -=item * TODO TESTS - -TODO tests are designed for maintaining an B<executable TODO list>. -These tests are expected NOT to succeed. If a TODO test does succeed, -the feature in question should not be on the TODO list, now should it? - -Packages should NOT be released with succeeding TODO tests. As soon -as a TODO test starts working, it should be promoted to a normal test -and the newly working feature should be documented in the release -notes or change log. - -=back - -=head1 RETURN VALUE - -Both C<ok> and C<skip> return true if their test succeeds and false -otherwise in a scalar context. - -=head1 ONFAIL - - BEGIN { plan test => 4, onfail => sub { warn "CALL 911!" } } - -While test failures should be enough, extra diagnostics can be -triggered at the end of a test run. C<onfail> is passed an array ref -of hash refs that describe each test failure. Each hash will contain -at least the following fields: C<package>, C<repetition>, and -C<result>. (The file, line, and test number are not included because -their correspondence to a particular test is tenuous.) If the test -had an expected value or a diagnostic string, these will also be -included. - -The B<optional> C<onfail> hook might be used simply to print out the -version of your package and/or how to report problems. It might also -be used to generate extremely sophisticated diagnostics for a -particularly bizarre test failure. However it's not a panacea. Core -dumps or other unrecoverable errors prevent the C<onfail> hook from -running. (It is run inside an C<END> block.) Besides, C<onfail> is -probably over-kill in most cases. (Your test code should be simpler -than the code it is testing, yes?) - -=head1 SEE ALSO - -L<Test::Harness> and, perhaps, test coverage analysis tools. - -=head1 AUTHOR - -Copyright (c) 1998-1999 Joshua Nathaniel Pritikin. All rights reserved. - -This package is free software and is provided "as is" without express -or implied warranty. It may be used, redistributed and/or modified -under the terms of the Perl Artistic License (see -http://www.perl.com/perl/misc/Artistic.html) - -=cut diff --git a/dh_getopt.pl b/dh_getopt.pl deleted file mode 100755 index 4d1d3903..00000000 --- a/dh_getopt.pl +++ /dev/null @@ -1,57 +0,0 @@ -#!/usr/bin/perl -# -# Because the getopt() program is so horribly broken, I wrote my own argument -# processer that uses the find Getopt::Long module. This is used by all -# debhelper shell scripts. -# -# Joey Hess, GPL copyright 1998. - -BEGIN { push @INC, "debian", "/usr/lib/debhelper" } -use strict; -use Dh_Getopt; - -# This is a tricky (and nasty) bit: override the error() function, which -# comes from Dh_Lib, with one of our own so we print out the list of errors -# to the shell, which can do what it wants with them. -sub Dh_Getopt::error { my $message=shift; - print "DH_PARSE_ERROR='$message'\n"; - exit 1; -} - -# Parse options. -my %options=Dh_Getopt::parseopts(); - -# Change a few lists in %options into strings, -# generate some options that only need to be visible to the -# shell scripts so Dh_Getopt doesn't bother generating. -$options{DOPACKAGES}=join " ",@{$options{DOPACKAGES}}; -if ($#{$options{EXCLUDE}} > -1) { - $options{EXCLUDE_GREP}=join '|', @{$options{EXCLUDE}}; -} -$options{EXCLUDE}=join " ",@{$options{EXCLUDE}}; - -# Check to see if DH_VERBOSE environment variable was set, if so, -# make sure verbose is on. -if (defined $main::ENV{DH_VERBOSE}) { - if ($main::ENV{DH_VERBOSE} ne undef) { - $options{VERBOSE}=1; - } -} - -# Check to see if DH_NO_ACT environment variable was set, if so, -# make sure no act mode is on. -if (defined $main::ENV{DH_NO_ACT}) { - if ($main::ENV{DH_NO_ACT} ne undef) { - $options{NO_ACT}=1; - } -} - -# Now output everything, in a format suitable for a shell to eval it. -foreach (keys(%options)) { - if (defined $options{$_}) { - print "DH_$_='$options{$_}'\n"; - } -} - -# This sets $@ in the shell to whatever arguements remain. -print "set -- @ARGV\n" diff --git a/dh_installmime.1 b/dh_installmime.1 deleted file mode 100644 index 4ace9985..00000000 --- a/dh_installmime.1 +++ /dev/null @@ -1,38 +0,0 @@ -.TH DH_INSTALLMIME 1 "" "Debhelper Commands" "Debhelper Commands" -.SH NAME -dh_installmime \- install mime files into package build directories -.SH SYNOPSIS -.B dh_installmime -.I "[debhelper options] [-n]" -.SH "DESCRIPTION" -dh_installmime is a debhelper program that is responsible for installing -mime files into package build directories. -.P -It also automatically generates the postinst and postrm commands needed to -interface with the debian mime-support package. See -.BR dh_installdeb (1) -for an explanation of how this works. -.P -If a file named debian/package.mime exists, then it is installed into -usr/lib/mime/packages/package in the package build directory. -.P -For the first first binary package listed in the control file, you may use -debian/mime instead. -.SH OPTIONS -.TP -.B debhelper options -See -.BR debhelper (1) -for a list of options common to all debhelper commands. -.TP -.B \-n, \--noscripts -Do not modify postinst/postrm scripts. -.SH ENVIRONMENT -See -.BR debhelper (1) -for a list of environment variables that affect all debhelper commands. -.SH "SEE ALSO" -.TP -.BR debhelper (1) -.SH AUTHOR -Joey Hess <joeyh@master.debian.org> diff --git a/dh_installmodules.1 b/dh_installmodules.1 deleted file mode 100644 index 6d9016fe..00000000 --- a/dh_installmodules.1 +++ /dev/null @@ -1,35 +0,0 @@ -.TH DH_INSTALLMODULES 1 "" "Debhelper Commands" "Debhelper Commands" -.SH NAME -dh_installmodules \- register modules with modutils -.SH SYNOPSIS -.B dh_installmodules -.I "[debhelper options] [-n]" -.SH "DESCRIPTION" -dh_installmodules is a debhelper program that is responsible for registering -kernel modules with modutils. -.P -A file named debian/package.modules (debian/modules my be used for the first -binary package in debian/control) will be installed as etc/modutils/package -in the package build directory. -.P -Then postinst and postrm commands are automatically generated to register -the modules when the package is installed. See -.BR dh_installdeb (1) -for an explanation of how this works. -.SH OPTIONS -.TP -.B debhelper options -See -.BR debhelper (1) -for a list of options common to all debhelper commands. -.TP -.B \-n, \--noscripts -Do not modify postinst/postrm scripts. -.SH ENVIRONMENT -See -.BR debhelper (1) -for a list of environment variables that affect all debhelper commands. -.SH "SEE ALSO" -.BR debhelper (1) -.SH AUTHOR -Joey Hess <joeyh@master.debian.org> diff --git a/dh_installpam.1 b/dh_installpam.1 deleted file mode 100644 index bb34a45c..00000000 --- a/dh_installpam.1 +++ /dev/null @@ -1,30 +0,0 @@ -.TH DH_INSTALLPAM 1 "" "Debhelper Commands" "Debhelper Commands" -.SH NAME -dh_installpam \- install pam support files -.SH SYNOPSIS -.B dh_installpam -.I "[debhelper options] [-n]" -.SH "DESCRIPTION" -dh_installpam is a debhelper program that is responsible for installing -files used by PAM into package build directories. -.P -If a file named debian/package.pam exists, then it is installed into -etc/pam.d/package in the package build directory. -.P -For the first first binary package listed in the control file, you may use -debian/pam instead. -.SH OPTIONS -.TP -.B debhelper options -See -.BR debhelper (1) -for a list of options common to all debhelper commands. -.SH ENVIRONMENT -See -.BR debhelper (1) -for a list of environment variables that affect all debhelper commands. -.SH "SEE ALSO" -.TP -.BR debhelper (1) -.SH AUTHOR -Joey Hess <joeyh@master.debian.org> diff --git a/dh_installxaw b/dh_installxaw deleted file mode 100755 index d71be544..00000000 --- a/dh_installxaw +++ /dev/null @@ -1,65 +0,0 @@ -#!/usr/bin/perl -w -# -# Integration with xaw-wrappers -# -# If debian/xaw-wrappers file exists, save it to -# $TMP/usr/lib/xaw-wrappers/conf/$PACKAGE -# -# Also, add calls to postinst and postrm. - -BEGIN { push @INC, "debian", "/usr/share/debhelper" } -use Dh_Lib; -init(); - -foreach $PACKAGE (@{$dh{DOPACKAGES}}) { - $TMP=tmpdir($PACKAGE); - $xaw=pkgfile($PACKAGE,'xaw'); - - if ($xaw ne '') { - if (! -d "$TMP/usr/lib/xaw-wrappers/config") { - doit("install","-d","$TMP/usr/lib/xaw-wrappers/config"); - } - doit("install","-p","-m644",$xaw, - "$TMP/usr/lib/xaw-wrappers/config/$PACKAGE"); - - if (! $dh{NOSCRIPTS}) { - # Parse the xaw conf file to figure out what programs - # and link names are present in it. Have to pass - # those into the scripts. - my %data; - my $install_opts=''; - my $remove_opts=''; - my $stanza=''; - - open (IN,$xaw); - while (<IN>) { - chomp; - s/\s+/ /g; - if (/^#/ eq '') { - if (/(.*?):\s?(.*)/) { - $data{lc($1)}=$2; - $stanza=1; - } - elsif ($stanza) { - $install_opts.="'$data{program} $data{'link-name'} $data{wrapped}' "; - $remove_opts.="'$data{'link-name'} $data{wrapped}' "; - undef %data; - $stanza=''; - } - } - } - close IN; - - if ($stanza) { - $install_opts.="'$data{program} $data{'link-name'} $data{wrapped}'"; - $remove_opts.="'$data{'link-name'} $data{wrapped}'"; - } - - autoscript($PACKAGE,"postinst","postinst-xaw", - "s:#OPTS#:$install_opts:"); - autoscript($PACKAGE,"prerm","prerm-xaw", - "s:#OPTS#:$remove_opts:"); - autoscript($PACKAGE,"postrm","postrm-xaw"); - } - } -} diff --git a/dh_installxaw.1 b/dh_installxaw.1 deleted file mode 100644 index 4fb9ebf6..00000000 --- a/dh_installxaw.1 +++ /dev/null @@ -1,40 +0,0 @@ -.TH DH_INSTALLXAW 1 "" "Debhelper Commands" "Debhelper Commands" -.SH NAME -dh_installxaw \- install xaw wrappers config files into package build directories -.SH SYNOPSIS -.B dh_installxaw -.I "[debhelper options] [-n]" -.SH "DESCRIPTION" -dh_installxaw is a debhelper program that is responsible for installing -xaw wrappers config files into package build directories. -.P -It also automatically generates the postinst, prerm, and postrm commands needed to -interface with the debian xaw-wrappers package. See -.BR dh_installdeb (1) -for an explanation of how this works. -.P -If a file named debian/package.xaw exists, then it is installed into -usr/lib/xaw-wrappers/config/package in the package build directory. -.P -For the first first binary package listed in the control file, you may use -debian/xaw instead. -.SH OPTIONS -.TP -.B debhelper options -See -.BR debhelper (1) -for a list of options common to all debhelper commands. -.TP -.B \-n, \--noscripts -Do not modify postinst/prerm/postrm scripts. -.SH ENVIRONMENT -See -.BR debhelper (1) -for a list of environment variables that affect all debhelper commands. -.SH "SEE ALSO" -.TP -.BR debhelper (1) -.TP -.BR update-xaw-wrappers (8) -.SH AUTHOR -Joey Hess <joeyh@master.debian.org> diff --git a/dh_listpackages b/dh_listpackages deleted file mode 100755 index 3ce48e06..00000000 --- a/dh_listpackages +++ /dev/null @@ -1,8 +0,0 @@ -#!/usr/bin/perl -w -# -# Output a list of all packages debhelper will act on. - -BEGIN { push @INC, "debian", "/usr/share/debhelper" } -use Dh_Lib; -init(); -print join("\n",@{$dh{DOPACKAGES}})."\n"; diff --git a/dh_listpackages.1 b/dh_listpackages.1 deleted file mode 100644 index aa4e7419..00000000 --- a/dh_listpackages.1 +++ /dev/null @@ -1,25 +0,0 @@ -.TH DH_LISTPACKAGES 1 "" "Debhelper Commands" "Debhelper Commands" -.SH NAME -dh_listpackages \- list binary packages debhelper will act on -.SH SYNOPSIS -.B dh_listpackages -.I "[debhelper options]" -.SH "DESCRIPTION" -dh_listpackages is a debhelper program that outputs a list of all binary -packages debhelper commands will act on. If you pass it some options, it -will change the list to match the packages other debhelper commands would -act on if passed the same options. -.SH OPTIONS -.TP -.B debhelper options -See -.BR debhelper (1) -for a list of options common to all debhelper commands. -.SH ENVIRONMENT -See -.BR debhelper (1) -for a list of environment variables that affect all debhelper commands. -.SH "SEE ALSO" -.BR debhelper (1) -.SH AUTHOR -Joey Hess <joeyh@master.debian.org> diff --git a/dh_perl.1 b/dh_perl.1 deleted file mode 100644 index cc2bb503..00000000 --- a/dh_perl.1 +++ /dev/null @@ -1,60 +0,0 @@ -.TH DH_PERL 1 "22 June 1999" "Debhelper Commands" "Debhelper Commands" -.SH NAME -dh_perl \- calculates perl scripts & modules dependencies -.SH SYNOPSIS -.B dh_perl -.I "[debhelper options] [-k] [-d] [library dirs ...]" -.SH "DESCRIPTION" -dh_perl is a debhelper program that is responsible for generating -the perl:Depends substitutions and adding them to substvars files. -.P -The program will look for the location of installed modules and will -use this information to generate a dependency (at the present time -it can only be perl5, perl5-thread, perl-5.00X or perl-5.00X-thread). -.P -It will also look at #! lines of perl scripts in order to be able -to calculate a dependency for perl scripts and not only perl modules. -.P -In addition it will automatically remove .packlist file and will -remove the directory in which it was if it's empty. You can -switch off this option by passing -k. -.SH OPTIONS -.TP -.TP -.B debhelper options -See -.BR debhelper (1) -for a list of options common to all debhelper commands. -.TP -.B -k -Keep .packlist files. -.TP -.B -d -In some specific cases you may want to depend on a -base package -(ie perl-5.00X-base or perl5-base). If so, you can pass -the -d option to make -.BR dh_perl -generate a dependency on the correct base package. This is only necessary -for some modules that are included in the base system. -.TP -.B library dirs -If your package does install perl modules in non-standard -directories, you can make -.BR dh_perl -check those directories by passing their names on the command line. -.BR dh_perl -will only check usr/lib/perl5 by default. -.SH ENVIRONMENT -See -.BR debhelper (1) -for a list of environment variables that affect all debhelper commands. -.SH "SEE ALSO" -.TP -.BR debhelper (1) -.SH "CONFORMS TO" -.P -Debian policy, version 2.5.0.0 -.P -Perl policy, version 1.0 -.SH AUTHOR -Raphaël Hertzog <hertzog@debian.org> diff --git a/dh_testversion.in b/dh_testversion.in deleted file mode 100644 index 9e2f14ef..00000000 --- a/dh_testversion.in +++ /dev/null @@ -1,23 +0,0 @@ -#!/bin/sh -e -# -# Debhelper version check. - -# Current version of debhelper is: -DH_VERSION=#DEBHELPER_VERSION# - -PATH=debian:$PATH:/usr/lib/debhelper -. dh_lib - -if [ "$1" -a "$2" ]; then - compare=$1 - ver=$2 -elif [ "$1" ]; then - compare=">=" - ver=$1 -fi - -if [ "$compare" -a "$ver" ] ; then - if ! dpkg --compare-versions $DH_VERSION $compare $ver; then - error "debhelper version $DH_VERSION is installed, but a version $compare $ver is needed to build this package." - fi -fi @@ -1,2 +0,0 @@ -x="debian|autoscripts" -find |grep -F "`echo "$x" | tr "|" "\n"`"
\ No newline at end of file diff --git a/from-debstd b/from-debstd deleted file mode 100644 index 31fd0cdd..00000000 --- a/from-debstd +++ /dev/null @@ -1,63 +0,0 @@ -Converting from debstd to debhelper: ------------------------------------ - -Debhelper is designed to be mostly backwards compatible to debstd. I say -mostly because I haven't made debhelper handle everything that debstd does -yet, and in a few cases, debhelper does things differently (and I hope, -better). - -In general, you can switch over to using debhelper as follows. In your -debian/rules, you currently will have some lines that read something like -this: - - debstd CHANGES TODO README - dpkg-gencontrol - dpkg --build debian/tmp .. - -Debhelper comes with a command called dh_debstd that mimics the behavior of -debstd, by calling various debhelper commands. So in the root directory of -your package you are converting, run: - - dh_debstd CHANGES TODO README --verbose --no-act - -Notice the parallel to the debstd command above, I just added "--verbose --act" -to the end. This will make dh_debstd output a list of commands that it thinks -will emulate what debstd would have done, without actually doing anything to -your package. The list will look similar to this: - - dh_installdirs - dh_installdocs TODO README - dh_installexamples - dh_installchangelogs CHANGES - dh_installmenu - dh_installcron - dh_installmanpages - dh_movefiles - dh_strip - dh_compress - dh_fixperms - dh_suidregister - dh_shlibdeps - dh_gencontrol - dh_makeshlibs - dh_installdeb - dh_md5sums - dh_builddeb - -Now copy that output into debian/rules, replacing the debstd command, as -well as any dpkg-gencontol and dpkg --build commands. - -Finally, debstd automatically modified postinst, postrm, etc scripts. Some -of the debhelper apps do that too, but they do it differently. Debstd just -appends its commands to the end of the script. Debhelper requires that you -insert a tag into your scripts, that will tell debhelper where to insert -commands. So if you have postinst, postrm, etc scripts, add a line reading -"#DEBHELPER#" to the end of them. - -Once you think it's all set up properly, do a test build of your package. If -it works ok, I recommend that you compare the new package and the old -debstd-generated package very closely. Pay special attention to the -postinst, postrm, etc scripts, and make sure that the new package contains -all the same files as the old, with the same permissions. - --- Joey Hess <joeyh@master.debian.org> diff --git a/pgptemp.$00 b/pgptemp.$00 deleted file mode 100644 index e69de29b..00000000 --- a/pgptemp.$00 +++ /dev/null |