Hi,
On Fri, 12 Aug 2011, Guillem Jover wrote:
> In addition such an interface cannot be expected to be used realiably
> by maintainers for all builds of their packages on buildds and
> similar or user systems, as it needs an additional setup step.
It's definitely not meant for maintainers... but it can be very useful
for derivatives distributions. I believe Ubuntu is doing stuff like
this with their pkgbinarymangler: for instance moving .mo files in
their language packs.
This precise wishlist is also a follow up of a discussion with a Maemo
developer who was looking for something similar.
It could also be useful for Emdebian to strip documentation at build time,
etc.
> At the point the build needs the builder to setup the environment
> variable, other more standard options can be used instead, like
> placing a wrapper in /usr/local/bin/dpkg-deb, dpkg-divert'ing,
> etc.
All those options need to implement the same option parsing logic than
dpkg-deb. While it's probably not hard, it's also busy work that can be
easily avoided.
I don't really see what's bad with this wishlist. If the environment
variable is not good, we can certainly consider a command line option
with a new /etc/dpkg/dpkg-deb.conf{,.d}. That would be cleaner indeed
as it allows to have several scripts invoked in the hook just like
dpkg --pre-invoke/--post-invoke.
(With the configuration file, it would also make it dead easy for a
derived distribution to use xz compression by default everywhere.)
Would the command-line option + config file approach be more acceptable to
you? I believe it's important to provide a clean way for others to do that
kind of customizations.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
