On Wed, Jul 10, 2013 at 6:30 PM, Dmitrijs Ledkovs wrote:
> I'd take a patch to dh-acc ;-)
Including it in dh-acc isn't interesting since that is a per-package
thing (AFAICT). For instance if the release team wanted to do an
archive-wide ABI check and automatically block libraries based on that
in
On 10 July 2013 09:20, Paul Wise wrote:
> On Wed, Jul 10, 2013 at 4:08 PM, Andrey Ponomarenko wrote:
>
>> There is a simple Perl script to do that:
>
> Thanks, what about including this capability in a-c-c itself?
>
I'd take a patch to dh-acc ;-)
>> my $Version = `dpkg -s $Package|grep Version`;
On Wed, Jul 10, 2013 at 4:08 PM, Andrey Ponomarenko wrote:
> There is a simple Perl script to do that:
Thanks, what about including this capability in a-c-c itself?
> my $Version = `dpkg -s $Package|grep Version`;
> chomp($Version);
> $Version=~s/\AVersion:\s*//g;
This would be better:
dpkg-qu
Paul Wise wrote:
I'm subscribed, no need to CC me.
On Tue, Jul 9, 2013 at 7:07 PM, Dmitrijs Ledkovs wrote:
One of the "library descriptors" that a-c-c supports is a list of
includes/directories.
Thus for $most packages just installing -dev package and pointing
a-c-c at the list of:
dpkg -L $p
I'm subscribed, no need to CC me.
On Tue, Jul 9, 2013 at 7:07 PM, Dmitrijs Ledkovs wrote:
> One of the "library descriptors" that a-c-c supports is a list of
> includes/directories.
> Thus for $most packages just installing -dev package and pointing
> a-c-c at the list of:
> dpkg -L $pkg-dev | gr
On 9 July 2013 10:18, Paul Wise wrote:
> On Wed, Jul 3, 2013 at 4:24 PM, Andrey Ponomarenko wrote:
>
>> So it is no need to create any input XML descriptors and compile header
>> files of a library anymore.
>>
>> However, this approach has some drawbacks. Perhaps the main drawback is the
>> inabil
On Wed, Jul 3, 2013 at 4:24 PM, Andrey Ponomarenko wrote:
> So it is no need to create any input XML descriptors and compile header
> files of a library anymore.
>
> However, this approach has some drawbacks. Perhaps the main drawback is the
> inability to perform some compatibility checks. For ex
>> Andrey Ponomarenko wrote:
>>> There is a new simple way to track changes in API/ABI of system
>>> libraries using a new ABI dumper [1] tool.
Hi,
in case someone wants to play with these tools, there are some packages
that should be analyzed.
On amd64 ldd reports symbol size mismatches in sev
Markus Raab wrote:
Hello!
Andrey Ponomarenko wrote:
There is a new simple way to track changes in API/ABI of system
libraries using a new ABI dumper [1] tool.
Thanks for the tipp!
However, this approach has some drawbacks. Perhaps the main drawback is
the inability to perform some compatibi
Hello!
Andrey Ponomarenko wrote:
> There is a new simple way to track changes in API/ABI of system
> libraries using a new ABI dumper [1] tool.
Thanks for the tipp!
> However, this approach has some drawbacks. Perhaps the main drawback is
> the inability to perform some compatibility checks. For
Hi Andrey,
On Wed, Jul 3, 2013 at 10:24 AM, Andrey Ponomarenko
wrote:
> Hi,
>
> There is a new simple way to track changes in API/ABI of system libraries
> using a new ABI dumper [1] tool. Just compile two library versions with -g
> additional option (to contain DWARF debug info) or take them fro
Hi,
There is a new simple way to track changes in API/ABI of system
libraries using a new ABI dumper [1] tool. Just compile two library
versions with -g additional option (to contain DWARF debug info) or take
them from the appropriate debug packages and create ABI dumps of both:
abi-dumper
12 matches
Mail list logo
