summaryrefslogtreecommitdiffstats
path: root/build-aux/edit-script.sh.in
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2020-05-14 19:05:30 +0200
committerAllan McRae <allan@archlinux.org>2020-09-23 09:12:01 +0200
commit406a37206f9afbc3731ac22eda5b45b5a15eddc5 (patch)
tree3daa0075785ea5eb760a8b67f905f181e4ea9d74 /build-aux/edit-script.sh.in
parent4533c6a8e0f39c7707e671b7f9687607b46f1417 (diff)
downloadpacman-406a37206f9afbc3731ac22eda5b45b5a15eddc5.tar.gz
pacman-406a37206f9afbc3731ac22eda5b45b5a15eddc5.tar.xz
makepkg: libprovides: don't provide both versioned and unversioned sonames
If multiple files match the pattern libfoo.so*, we want to check each of them and see if they are shared libraries, and if so, if they have versions attached. But some packages can have both shared libraries and random files which match the filename pattern. This is true at least for files in /usr/share/gdb/auto-load/, which must match the filename they are paired with, followed by "-gdb.py" (or some other gdb scripting ext), but definitely don't contain a shared library. In this case, we don't want to double-report the library in the generated provides. It's also possible (probably) for a package to provide a versioned as well as an unversioned shared library, but in such cases a single provides entry is sufficient to cover both cases (and the libdepends for the depending package would contain an unversioned dependency). Solve this by keeping track of whether we have added a versioned soname provides already, and then only adding a maximum of one unversioned provides *iff* there isn't a versioned one yet. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'build-aux/edit-script.sh.in')
0 files changed, 0 insertions, 0 deletions