Re: Riddled by debian-policy 8.1.1 about ldconfig (original) (raw)
- To: Thomas Schmitt <scdbackup@gmx.net>
- Cc: debian-mentors@lists.debian.org
- Subject: Re: Riddled by debian-policy 8.1.1 about ldconfig
- From: Charles Plessy <plessy@debian.org>
- Date: Thu, 14 Sep 2017 23:31:48 +0900
- Message-id: <[π] 20170914143148.pttxllofnlzu7zel@falafel.plessy.net>
- Mail-followup-to: Thomas Schmitt <scdbackup@gmx.net>, debian-mentors@lists.debian.org
- In-reply-to: <[π] 21753757030521101177@scdbackup.webframe.org>
- References: <[π] 21753757030521101177@scdbackup.webframe.org>
Le Thu, Sep 14, 2017 at 02:25:41PM +0200, Thomas Schmitt a Γ©crit :
What is meant by "DEBIAN/triggers" in policy manual and man 5 deb-triggers ? Is there supposed to be a "DEBIAN" directory under ./debian ?
Hi Thomas,
the DEBIAN
directory is created in the process of building in binary
packages. In the binary packages themselves, its contents become the
contents of the control.tar.gz
member. For a package "p", the file
DEBIAN/triggers is installed in /var/lib/dpkg/info/p.triggers
. You
can find many real examples there. In particular, for libraries
complying with the Policy, you will see that this file indeed
"activate-noawait" the "ldconfig" trigger. For packages built using
Debhelper, the triggers files is added by dh_makeshlibs
, which
explains why you can not see traces of it in the clean source package.
I hope it clarifies.
Have a nice day,
-- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan
Reply to:
- References:
- Riddled by debian-policy 8.1.1 about ldconfig
* From: "Thomas Schmitt" scdbackup@gmx.net
- Riddled by debian-policy 8.1.1 about ldconfig
- Prev by Date:Bug#875679: closing 875679
- Next by Date:Bug#875804: RFS: robocut/1.0.11-1-- Control program for Graphtec cutting plotters
- Previous by thread:Riddled by debian-policy 8.1.1 about ldconfig
- Next by thread:Re: Riddled by debian-policy 8.1.1 about ldconfig
- Index(es):