On Mon, 21 Mar 2011, Steve Langasek wrote:
> Attached is a patch to update policy's FHS exception to reflect the current
> consensus among the gcc, eglibc, and dpkg maintainers around the paths to
> use for implementation and the interface packages should use to query these
> paths.
[...]
> From 1f
Package: debian-policy
Version: 3.9.1.0
Dear Policy maintainers,
A not-so-recent bug report, #230308, raised the issue of how a long-running
program which would be broken (until restart) by a major Perl package upgrade
(eg from 5.10 to 5.12) could be notified of such a restart. There was a rough
Dominic Hargreaves wrote:
> A not-so-recent bug report, #230308, raised the issue of how a long-running
> program which would be broken (until restart) by a major Perl package upgrade
> (eg from 5.10 to 5.12) could be notified of such a restart. There was a rough
> consensus on that bug report tha
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was jrnie...@gmail.com).
> usertags 619275 = informative
Bug#619275: Perl Policy change to document major version upgrade trigger
There were no usertags set.
The Multiarch specification only covers libraries and does not
specifically deal with include files.
To make multiarch useful for cross-building as well as co-installation of
libraries we need to install headers to /usr/include/, which
needs an FHS exception.
Here is a patch to policy to allow
5 matches
Mail list logo
