Processing commands for [EMAIL PROTECTED]:
> retitle 87828 [ACCEPTED 14/03/2001] Deprecate confusing Build-Depends arch
> syntax
Bug#87828: [PROPOSAL] Deprecate confusing Build-Depends arch syntax
Changed Bug title.
> severity 87828 normal
Bug#87828: [ACCEPTED 14/03/2001] Deprecate confusing Bui
On Wed, Mar 14, 2001 at 01:29:56PM +0100, Wichert Akkerman wrote:
> Previously Julian Gilbey wrote:
> > Is there any easy way in which dpkg-statoverride can be modified to
> > distinguish between local and package overrides, in the way that
> > suidmanager used to do?
>
> There are only local over
Package: debian-policy
Version: 3.5.2.0
Severity: wishlist
Proposed patch:
Any package installing shared libraries in a directory that's listed
in `/etc/ld.so.conf' or in one of the default library directories of
`ld.so' (currently, these are `/usr/lib' and `/lib') must call
`
Previously Julian Gilbey wrote:
> 7.2 Binary dependencies
> This section states that "All but Pre-Depends and Conflicts take
> effect only when a package is to be configured." But actually,
> dpkg appears to ignore everything except for (Pre-)Depends,
> (sometimes) Recommends and C
Mark Baker wrote:
> As I understand it, debian distributing stripped binaries that originally
> had symbols in (rather than not putting them in in the first place) means
> that if I get a non-stripped binary it should have everything at the same
> addresses as the distributed one so should let me d
Here are my thoughts on significant points in chapters 7-10,
continuing the series.
7.2 Binary dependencies
This section states that "All but Pre-Depends and Conflicts take
effect only when a package is to be configured." But actually,
dpkg appears to ignore everything except for (Pre
On 13-Mar-01, 13:05 (CST), Ben Gertzfield <[EMAIL PROTECTED]> wrote:
> > "Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
>
> Wichert> Policy should set guidelines for making packages [...]
>
> Wichert> The less details, the better.
>
> Um. Policy *IS* the guide for making
Previously Julian Gilbey wrote:
> Is there any easy way in which dpkg-statoverride can be modified to
> distinguish between local and package overrides, in the way that
> suidmanager used to do?
There are only local overrides now.
Wichert.
--
_
On Tue, Mar 13, 2001 at 04:42:46PM +0100, Wichert Akkerman wrote:
> Previously Julian Gilbey wrote:
> > dpkg-statoverride --list is OK, adding or removing overrides is almost
> > certainly not.
>
> It most certainly is. Think dynamic useres and groups, user interaction
> if debconf isn't availabl
On Wed, Mar 14, 2001 at 12:57:42PM +1100, Drew Parsons wrote:
> > > Seems to me there's still a gaping hole in policy though. Is
> > > packages.debian.org really supposed to be the definitive arbiter of policy
> > > with regards to sections? The grep-available trick is obscure enough to
> > > no
10 matches
Mail list logo
