Sven Mueller wrote:
> Also true, but as I frequently need to backport packages to (old)stable,
> I would really like people only to increase the debhelper compat level
> if they really _use_ new features in the new level.
>
> While I backported packages to sarge during the etch release cycle, I
>
Steinar H. Gunderson wrote on 09/07/2007 16:57:
> On Mon, Jul 09, 2007 at 04:48:05PM +0200, Bruno Costacurta wrote:
>> Hello,
>> what is the policy about file debian/compat ?
>
> It's a part of the interface to debhelper, and as such is documented in the
> debhelper documentation.
True.
>> I was
Hi Bruno
* Bruno Costacurta <[EMAIL PROTECTED]> [2007-07-09 16:53]:
> what is the policy about file debian/compat ?
There is no policy for compat since compat specifies the
compatibility level of the debhelper tools and you don't
need to build your packages with debhelper.
> I was not able to f
On Mon, Jul 09, 2007 at 04:48:05PM +0200, Bruno Costacurta wrote:
> Hello,
> what is the policy about file debian/compat ?
It's a part of the interface to debhelper, and as such is documented in the
debhelper documentation.
> I was not able to find any policy about it in 'Debian Policy Manual' on
On Mon, 2007-07-09 at 16:48 +0200, Bruno Costacurta wrote:
> what is the policy about file debian/compat ?
>
> I was not able to find any policy about it in 'Debian Policy Manual' on
> debian.org. It seems it should contain package version mentionned in
> field 'Build-depends:' in debian/control
5 matches
Mail list logo
