Sam Hartman:
>> "Ximin" == Ximin Luo writes:
>
> Ximin> Jakob Leben:
> >> I have a system for updating my own software which is also
> >> deployed
>
> Ximin> If you Depends: libfoo8, this will prevent dpkg from
> Ximin> upgrading the library from libfoo8 to libfoo9 until
> "Jakob" == Jakob Leben writes:
Jakob>Well, there are use cases that are not so simple. For
Jakob> example: I might deploy Debian 9.1 on an embedded machine
Jakob> sold to a client on the other side of the world. I have a
Jakob> system for updating my own software which i
Jakob Leben:
> I have a system for updating my own software which is also deployed on that
> machine, but not the rest of the Debian system. Now, if ABI might change
> between 9.2, then I have no guarantee that if I test my software update with
> 9.2, it will be work as expected on the client's
On Sun, Mar 17, 2019 at 12:11 AM Ximin Luo wrote:
>
> In general, if no documented guarantee exists then you should assume there
> is no guarantee.
>
That's what I thought too.
If you are a developer and you link against a particular version of a
> library in Debian 9.1 and its ABI changes in
Jakob,
the backward incompatible ABI changes are generally something we avoid in
stable releases.
There might be occasional exception to the rule where it cannot be avoided, but
it is not something we take lightly.
Ondrej
--
Ondřej Surý
> On 17 Mar 2019, at 08:10, Ximin Luo wrote:
>
> Jak
Jakob Leben:
> Hello,
>
> I have not been able to find clear information about Debian policies for ABI
> compatibility across point releases and security updates. I would assume that
> no ABI changes at all (backwards compatible or not) are allowed in point
> releases and security updates. Stil
6 matches
Mail list logo
