pcp
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [pcp] pcp updates: packaging/build changes for latest Debian version

from [Ken McDonell] [Permanent Link][Original]
To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates: packaging/build changes for latest Debian version
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 6 May 2016 10:32:57 +1000
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1733941836.45640958.1462494259580.JavaMail.zimbra@xxxxxxxxxx>
References: <572BBB8F.90703@xxxxxxxxxxxxxxxx> <1733941836.45640958.1462494259580.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 
On 06/05/16 10:24, Nathan Scott wrote:



----- Original Message -----

[...]
commit ba916746ae5b979a18797410627710a0a6b631b1
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Fri May 6 07:25:09 2016 +1000

      debian/rules: disable dbgsym packages

      Turned on by default in post-jessie Debian versions, but does not
      play well with existing PCP packaging.


https://lists.debian.org/debian-devel/2015/12/msg00262.html

Suggests setting DEB_BUILD_OPTIONS=noddebs in the environment is an alternative
we might be able to use here - might have better back-compat properties than
using a command line option?  (could be set in Makepkgs with the other DEB_*?)
That URL contains other misleading info, ... I think this is closer to the truth https://wiki.debian.org/AutomaticDebugPackages
Anyway, the command-line option generates a warning but is otherwise benign on the older releases, AFAICT.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [pcp] pcp updates: multithreading etc., Ken McDonell
Next by Date:  Re: [pcp] pcp updates: multithreading etc., Frank Ch. Eigler
Previous by Thread:  Re: [pcp] pcp updates: packaging/build changes for latest Debian version, Nathan Scott
Next by Thread:  [no subject], Suyash
Indexes:  [Date] [Thread] [Top] [All Lists]