On 07/06/15 11:26, Chris Boot wrote:
[...]
> One of the first tasks on my list is to resolve the issue with
> dependencies and ABI compatibility surrounding the building of ppp
> plugins.
[...]
Hi folks,
During this week's Mini-debconf in Cambridge I have worked a lot on ppp
and I believe that I
[Chris Boot]
> There probably doesn't need to be an ABI break for every version, but
> there is with 2.4.6 => 2.4.7 due to the addition of some variables. If
> this was a shared library it wouldn't necessitate a soname bump as it's
> essentially just a new symbol, but a plugin that happens to use
Chris Boot wrote...
> The main problem that I see is that there isn't a built-in mechanism for
> tracking such a situation, as far as I can tell. There aren't any shared
> libraries involved, so I don't have the benefit of sonames, symbols
> files or symbol versioning.
(...)
disclaimer: I might
Hi all,
I'm emailing again because I realise I got the per-package QA email
addresses all wrong, but also because I don't think we came to any real
resolution on this.
My original message:
On 07/06/15 11:26, Chris Boot wrote:
> Hi all,
>
> Apologies for the long email, but there's a lot to disc
On Sun, Jun 07, 2015 at 11:26:12AM +0100, Chris Boot wrote:
> One of the first tasks on my list is to resolve the issue with
> dependencies and ABI compatibility surrounding the building of ppp
> plugins. Several packages in the archive use the ppp-dev package to help
> them build ppp plugins that
Am 07.06.2015 um 13:35 schrieb Chris Boot:
> On 07/06/15 11:49, Michael Biebl wrote:
>> Thinking about this, something like this could be useful for such
>> situations:
>> Breaks: != ppp-abi-version-2.4.6
>> as counterpart to
>> Depends: = ppp-abi-version-2.4.6
>
> We can't do that quite, but this
On 07/06/15 12:35, Chris Boot wrote:
> On 07/06/15 11:49, Michael Biebl wrote:
>> Shipping a .pc file upstream to get the correct plugin directory (and
>> build flags) sounds like a useful addition.
>
> Upstream's build system is... archaic. It doesn't autotools and its
> configure script is hand-
On 07/06/15 11:49, Michael Biebl wrote:
> Am 07.06.2015 um 12:26 schrieb Chris Boot:
>> network-manager only has pppd as a Recommends despite shipping a pppd
>> plugin.
>
> Small correction: network-manager has a versioned Recommends and a
> versioned Breaks against ppp.
> This is deliberate, sinc
On Sun, Jun 7, 2015 at 7:00 PM, Michael Biebl wrote:
> Thinking about this, something like this could be useful for such
> situations:
> Breaks: != ppp-abi-version-2.4.6
> as counterpart to
> Depends: = ppp-abi-version-2.4.6
I'm not sure you can do the Breaks part of that as it would have to be
l
Am 07.06.2015 um 12:49 schrieb Michael Biebl:
> Am 07.06.2015 um 12:26 schrieb Chris Boot:
>> network-manager only has pppd as a Recommends despite shipping a pppd
>> plugin.
>
> Small correction: network-manager has a versioned Recommends and a
> versioned Breaks against ppp.
> This is deliberate
Am 07.06.2015 um 12:26 schrieb Chris Boot:
> network-manager only has pppd as a Recommends despite shipping a pppd
> plugin.
Small correction: network-manager has a versioned Recommends and a
versioned Breaks against ppp.
This is deliberate, since network-manager does not strictly need ppp.
The ve
* Chris Boot , 2015-06-07, 11:26:
Depends: [...] ppp (>= 2.4.6~), ppp (<< 2.4.7~) [...]
The tildes are pointless here.
s/~//g
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
Hi all,
Apologies for the long email, but there's a lot to discuss on the topic.
Marco d'Itri and I recently agreed that I would take over maintenance of
ppp. Thanks for all your hard work over the years keeping this package
going, Marco.
One of the first tasks on my list is to resolve the issue
13 matches
Mail list logo
