lvc / abi-monitor Goto Github PK

We need to add support for the Meson build system out of the box to not to write a custom build script per each library.

Libraries moved to meson:

• colord
• dconf
• libfuse
• libgusb

Hi -

Thanks for your cool tool.

I have it set up on a cronjob to output daily updates for my project here

https://libwebsockets.org/abi/timeline/libwebsockets/index.html

However, on master there is no attempt to keep a history in git. If there are problems in patches from the last day or two, or sometimes further back, the patches are simply rewritten with the fix. The stable branches are treated as "patches on top" -only history branches.

This makes trouble for abi-monitor, because he wants to use git pull. git pull will reject the fast forward normally, if the update breaks history so you "lose" content in your current HEAD.

I can work around it by editing abi-monitor script to use "git fetch" instead. But it'd perhaps be better if there was some way to select this in the config.

Thanks.

https://salsa.debian.org/cinemast-guest/abi-monitor/blob/master/debian/patches/0001-typo.patch

Hi
The abi-monitor tool needs to set the BuildDir parameter in the profile to avoid the scenarios where the configure, autogen.sh and meson.build files are not in the first level directory of the package. However, there are special scenarios: for example, the compiled files of expat2.1.0 are in the first level, while expat2.2.9 is in the deep level path. In this case, setting parameters can not solve the path problem. Can set the BuildDir path for each version？
Thanks.

Hi Andrey!

There are some license inconsistencies. The header of your source files declare GPL or Lesser GPL. The statement is missing a version or a minimal version.

The LICENSE file mentions GPL-2 or Library GPL-2.

Could you please clarify this?

Hi all,

1. i am using abi-monitor tool bellow command is download particular kernel
   abi-monitor -get -v 5.15.38 linux.json
2. this above command is working fine but after the download i am trying to build that kernel version that's why i am passing bellow
   command
   abi-monitor -build -v 5.15.38 linux.json

but its not build properly its showing error in bellow

ERROR : custom build has failed (exit code 256)
ERROR : failed to build

any one please help me,

In our project main development happens on two branches, which we would like to build. Could you please add a way to specify additional Git/SVN branches to be regularly rebuilt in the same way as "current" branch is?

Hi Andrey!

Thanks for providing abi-monitor, it's a great tool.

Could you please provide a changelog for abi-monitor (and also abi-tracker)? It makes the life of package maintainers easier.