pcp
[Top] [All Lists]

Re: [pcp] pcp updates - last piece of debian packaging changes for this

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates - last piece of debian packaging changes for this round
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 28 Feb 2014 11:40:06 +1100
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <722030351.18148411.1393537152651.JavaMail.zimbra@xxxxxxxxxx>
References: <530F9B64.4080505@xxxxxxxxxxxxxxxx> <722030351.18148411.1393537152651.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
On 28/02/14 08:39, Nathan Scott wrote:
Hi Ken,

This part does not look like a valid solution - the "official"
buildd builds use the build dependencies to populate the build
root, so we have a chicken-and-egg situation here.  In the end
this would result in this code no longer being built even when
it should be (in Debian release builds, not our local builds).

OK, I'll put it back, but without a version number and let our build/configure magic decide if the version is new enough to build and package pcp-webapi.

----- Original Message -----
[...]
     debian build - remove Build-Depends for libmicrohttpd-dev

     We handle this in the configure and packaging now ... if the right
     libmicrohttpd-dev is installed we build the pcp-webapi package, otherwise
     it is neither built nor packaged.

Are these distros without microhttpd really current? ...

Yes ... MOST of the debian-derived ones in my QA farm ... sigh.

... If even
RHEL5 has it (which it does) I'm amazed that there are current
Debian variants that do not ... ?  Can this problem be solved
by using more recent versions of these distros?

Er, no. Not that I can see from using the official package repositories.

<Prev in Thread] Current Thread [Next in Thread>