summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAge
* In v8 mode, do not allow directly passing unknown options to debhelper ↵Joey Hess2010-05-23
| | | | commands. (Unknown options in DH_OPTIONS still only result in warnings.)
* Add deprecation warning for dh_clean -k.Joey Hess2010-05-23
|
* updateJoey Hess2010-05-12
|
* updateJoey Hess2010-04-08
|
* releasing version 7.4.16Joey Hess2010-04-06
|
* If neither -a or -i are specified, debhelper commands used to default to ↵Joey Hess2010-03-01
| | | | acting on all packages in the control file, which was a guaranteed failure if the control file listed packages that did not build for the target architecture. After recent optimisations, this default behavior can efficiently be changed to the more sane default of acting on only packages that can be built for the current architecture. This change is mostly useful when using minimal rules files with dh. Closes: #572077
* todoJoey Hess2010-02-16
|
* updateJoey Hess2009-12-29
|
* stop trying to handle substvars idempotentlyJoey Hess2009-12-29
| | | | | | | | | | | | | | | | | | | | | | | In the beginning, I tried to be careful to have commands that added a substvar remove it when ran again with different options that caused it to not be needed. However, now when I look over the code, I see 3 places that got it right, 1 that was right but I just broke, and a dozen that don't even try to handle this case. Also, handling the case is hard; code that adds substvars may be complex and calculate versioned dependencies. The removal code then has to somehow also come up with those same exact dependency strings. It's a recipe for nasty code and maintenance headache even if I went and fixed everything right now. Instead, I dropped the whole thing. Many debhelper commands make no pretense of being idempotent anyway; it's easy and normal to call dh_prep when starting a binary package build, with the exact purpose of not needing to worry about idempotency. I did leave in the delsubstvar function, as well as the option to addsubstvar that, confusingly, causes an item to be removed. Just for library compatability reasons.
* releasing version 7.4.10Joey Hess2009-12-09
|
* Drop deprecated programs from the list of commands in debhelper(7). Closes: ↵Joey Hess2009-11-04
| | | | #548382
* updateJoey Hess2009-11-04
|
* Add deprecation warnings for -u to the documentation, since putting options ↵Joey Hess2009-11-04
| | | | after -- is much more sane. (However, -u will not go away any time soon.) Closes: #554509
* -a == -sJoey Hess2009-09-01
| | | | | | | The -a flag now does the same thing as the -s flag, so debhelper users do not need to worry about using the -s flag when building a package that only builds for some architectures, and dh will also work in that situation. Closes: #540794
* drop regex support from remove_command_optionsJoey Hess2009-08-26
| | | | | | | | | | | | | I hope that it will not be needed; indeed I doubt that remove_command_options will be used much, because sequence addons would need to try to do conflicting things to need it. And the interface makes it hard for such conflicting sequence addons to work around the other, since addons can be loaded in either order. So let's not encourage them too much, and if there's a use case later, we can made changes. I haven't applied Modestas's enhanced patch that allows adding an option to all commands because I similarly think it might not be used. If a use case comes along we can add something like that.
* Allow dh addons to pass options to debhelper commandsModestas Vainius2009-08-26
| | | | | | | | Add dh addons APIs add_command_options()/remove_command_options() that allow addons to add additional options which dh will pass to the specified debhelper commands. Signed-off-by: Modestas Vainius <modestas@vainius.eu>
* releasing version 7.3.12Joey Hess2009-08-06
|
* dh: Allow creation of new sequences (such as to handle a patch target for ↵Joey Hess2009-08-06
| | | | quilt), by adding an add_command function to the sequence addon interface. See #540124.
* mention configureJoey Hess2009-07-01
|
* misc minor changesJoey Hess2009-06-29
|
* clean up --sourcedir/--sourcedirectory conflictJoey Hess2009-06-28
| | | | | | | | | | | | * Move two move command-specific options to only be accepted by the commands that use them. The options are: --sourcedir, --destdir * If any third-party debhelper commands use either of the above options, they will be broken, and need to be changed to pass options to init(). This was done because of a conflict with the --sourcedirectory options used by dh_auto_*. I originally wanted to make dh_auto_* and dh_install both use --sourcedir, but that didn't work out.
* Merge branch 'master' into buildsystemsJoey Hess2009-06-11
|\ | | | | | | | | Conflicts: debian/changelog
| * dh_scrollkeeper: Now a deprecated no-op. Closes: #530806Joey Hess2009-05-27
| |
* | updateJoey Hess2009-04-20
| |
* | basic docs about buildsystem classesJoey Hess2009-04-20
|/
* Move dh sequence documentation to PROGRAMMING.Joey Hess2009-04-20
|
* updateJoey Hess2009-04-10
|
* document load_load, write_logJoey Hess2009-03-23
|
* remove item already doneJoey Hess2009-03-07
|
* Compatability level 4 is now deprecated.Joey Hess2009-03-07
|
* updateJoey Hess2009-02-15
|
* Move many command-specific options to only be accepted by the command that ↵Joey Hess2008-10-21
| | | | | | | | | | | | | | | | | | uses them. Affected options are: -x, -r, -R, -l, -L, -m, --include-conffiles, --no-restart-on-upgrade, --no-start, --restart-after-upgrade, --init-script, --filename, --flavor, --autodest, --libpackage, --add-udeb, --dpkg-shlibdeps-params, --dpkg-gencontrol-params, --update-rcd-params, --major, --remove-d, --dirs-only, --keep-debug, --version-info, --list-missing, --fail-missing, --language, --until, --after, --before, --remaining, --with * If any third-party debhelper commands use any of the above options, they will be broken, and need to be changed to pass options to init(). * To avoid breaking rules files that pass options to commands that do not use them, debhelper will now only warn if it encounters an unknown option. This will be converted back to an error later.
* Allow individual debhelper programs to define their own special options by ↵Joey Hess2008-10-21
| | | | passing a hash to init(), which is later passed on the Getopt::Long. Closes: #370823
* updateJoey Hess2008-06-19
|
* dh_installinit: Add --restart-after-upgrade, which avoids stopping a daemon ↵Joey Hess2008-05-08
| | | | in the prerm, and instead restarts it in the postinst, keeping its downtime minimal. Since some daemons could break if files are upgraded while they're running, it's not the default. It might become the default in a future (v8) compatability level. Closes: #471060
* docsJoey Hess2008-04-30
|
* dh_prep: New program, does the same as dh_clean -k (which will be deprecated ↵Joey Hess2008-04-23
| | | | later).
* finialize v6 modeJoey Hess2008-01-07
|
* r2037: Vcs- fields are now officialjoeyh2007-10-10
|
* r1988: releasing version 5.0.45joeyh2007-04-13
|
* r1980: * prerm and postrm scripts are now generated in a reverse order thanjoeyh2007-04-09
| | | | | | | | | | | | | | | | | preinst and postinst scripts. For example, if a package uses dh_pysupport before dh_installinit, the prerm will first stop the init script and then remove the python files. * Introducing beginning of v6 mode. * dh_installwm: In v6 mode, install a slave manpage link for x-window-manager.1.gz. Done in v6 mode because some window managers probably work around this longstanding debhelper bug by registering the slave on their own. This bug was only fixable once programs moved out of /usr/X11R6. Closes: #85963 * dh_builddeb: In v6 mode, fix bug in DH_ALWAYS_EXCLUDE handling, to work the same as all the other code in debhelper. This could only be fixed in v6 mode because packages may potentially legitimately rely on the old buggy behavior. Closes: #242834 * dh_installman: In v6 mode, overwrite exsiting man pages. Closes: #288250
* r1979: already done!joeyh2007-04-09
|
* r1941: * ACK last three NMUs with thanks to Raphael Hertzog for making the ↵joeyh2006-10-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | best of a difficult situation. * Revert all dh_python changes. Closes: #381389, #378604 * Conflict with python-support << 0.5.3 and python-central << 0.5.5. * Make dh_python do nothing if debian/pycompat is found. The new versions of dh_pysupport or dh_pycentral will take care of everything dh_python used to do in this situation. * dh_python is now deprecated. Closes: #358392, #253582, #189474 * Non-maintainer upload. * Update of dh_python - when buidling for a non-standard Python version, generate more reasonable Depends like "python (>= X.Y) | pythonX.Y" Closes: #375576 - fix handling of private extensions. Closes: #375948 - fix parsing of XS-Python-Version, it didn't work if only fixed versions were listed in XS-Python-Version. - fix use of unitialized value. Closes: #374776 - fix typos in POD documentation. Closes: #375936 * Non-maintainer upload. * Update of dh_python - vastly refactored, easier to understand, and the difference between old policy and new policy is easier to grasp - it supports an -X option which can be used to not scan some files - uses debian/pyversions as reference source of information for dependencies but also parse the XS-Python-Version header as fallback. - ${python:Versions}'s default value is XS-Python-Version's value instead of "all" when the package doesn't depend on a specific python version. Closes: #373853 - always generate ${python:Provides} and leave the responsibility to the maintainer to not use ${python:Provides} if he doesn't want the provides. - uses debian/pycompat or DH_PYCOMPAT as reference field to run in new policy mode. The presence of XS-Python-Version will also trigger the new policy mode (this is for short-term compatibility, it may be removed in the not too-distant future). DH_PYCOMPAT=1 is the default mode and is compatible to the old policy. DH_PYCOMPAT=2 is the new mode and is compatible with the new policy. * Use "grep ^Version:" instead of "grep Version:" on the output of dpkg-parsechangelog since the above changelog entry matched "Version:" and thus made the build fail. * Non-maintainer upload. * Integrate the new dh_python implementing the new Python policy. Closes: #370833
* r1938: updatejoeyh2006-07-26
|
* r1923: updatejoeyh2006-06-03
|
* r1871: * dh_makeshlibs: add support for adding udeb: lines to shlibs filejoeyh2006-01-28
| | | | via --add-udeb parameter. Closes: #345471
* r1864: releasing version 5.0.19joeyh2006-01-24
|
* r1859: * Reverted change in 4.1.9, so generation of EXCLUDE_FIND escapes "." tojoeyh2006-01-20
| | | | | | | | "\\.", which turns into "\." after being run through the shell, and prevents find from treating -X.svn as a regexp that matches files such as foo/svn.vim. (It's safe to do this now that all uses of EXCLUDE_FIND are via complex_doit(), which was not the case of dh_clean when this change was originally made.) Closes: #349070
* r1849: * dh_installinit: If run with -o, do the inverse of -n and onlyjoeyh2006-01-08
| | | | | | | | | set up maintainer script snippets, w/o installing any files. Useful for those edge cases where the init script is provided by upstream and not easily installed by dh_installinit but where it's worth letting it manage the maintainer scripts anyway. Closes: #140881, #184980 * -o might be added for other similar commands later if there is any reason to. And yeah, it means that -no is close to a no-op..
* r1805: releasing version 5.0.0joey2005-11-02
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-25 16:01:21 +0000