FM / dpkg-dev

/usr/share/doc/dpkg-dev

Name	Size	Mode	Actions
AUTHORS	1234	0644	edit dl rm
changelog.Debian.gz	4493	0644	edit dl rm
copyright	7882	0644	edit dl rm
frontend.txt	1094	0644	edit dl rm
README.api	1550	0644	edit dl rm
README.feature-removal-schedule.gz	2239	0644	edit dl rm
rootless-builds.txt.gz	2894	0644	edit dl rm
THANKS.gz	3326	0644	edit dl rm
triggers.txt.gz	11693	0644	edit dl rm
usertags.gz	1847	0644	edit dl rm

Edit: /usr/share/doc/dpkg-dev/frontend.txt (1094B)

Frontend Interfaces
===================

This file will try to document some of the interfaces that dpkg makes
available to frontends or that expects them to use, which are currently
not covered by any other type of documentation.

Database Locking
----------------

Any frontend needing to make sure no write operation is currently happening,
and no other frontend is running should first acquire the frontend lock at
«<admindir>/lock-frontend», and then acquire the dpkg database lock at
«<admindir>/lock». When the frontend invokes dpkg, it should set the
environment variable DPKG_FRONTEND_LOCKED (to prevent dpkg from acquiring
the frontend lock), and then release the dpkg database lock, which will be
acquired by dpkg itself. This way no other frontend following this protocol
can race to perform operations while another one has one in progress.

These locks must be file record locks (i.e. fcntl(2) advisory locking), and
the whole file should be locked, as that's the most portable way to perform
this operation; this can be achieved by using start=0, len=0 and
whence=SEEK_SET.

Frontend Interfaces =================== This file will try to document some of the interfaces that dpkg makes available to frontends or that expects them to use, which are currently not covered by any other type of documentation. Database Locking ---------------- Any frontend needing to make sure no write operation is currently happening, and no other frontend is running should first acquire the frontend lock at «/lock-frontend», and then acquire the dpkg database lock at «/lock». When the frontend invokes dpkg, it should set the environment variable DPKG_FRONTEND_LOCKED (to prevent dpkg from acquiring the frontend lock), and then release the dpkg database lock, which will be acquired by dpkg itself. This way no other frontend following this protocol can race to perform operations while another one has one in progress. These locks must be file record locks (i.e. fcntl(2) advisory locking), and the whole file should be locked, as that's the most portable way to perform this operation; this can be achieved by using start=0, len=0 and whence=SEEK_SET.