From: gt7-void <gt7-void@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] sorted common/shlibs to avoid merge/rebase conflicts
Date: Mon, 05 Apr 2021 01:17:10 +0200 [thread overview]
Message-ID: <20210404231710.sZP3qD0vBnOyt1wiJ4jQvVFtkOGY0IOli7_Rfynjx-g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
New comment by gt7-void on void-packages repository
https://github.com/void-linux/void-packages/issues/29965#issuecomment-813114661
Comment:
Regarding duplicates, there are many different situations:
- exact duplicate lines are obvious to remove, but harmless
- Something like this:
```
ld.so.1 glibc-2.32_1 mips
ld.so.1 glibc-2.32_1 ppc
```
May be ok, although the documentation for the third field is unclear.
- what about this:
```
libClp.so.1 CoinMP-1.8.3_1
libClp.so.1 libClp-1.16.11_1
```
using `xlocate` shows that both packages ship `/usr/lib/libClp.so.1`, but they don't conflict to each other.
- what about this:
```
libGLESv2.so.2 libGLES-1.0_1
libGLESv2.so rpi-userland-0.0.0.0.20150907_1
libGLESv2.so atom-1.41.0_1
libGLESv2.so opera-55.0.2994.37_2
libGLESv2.so discord-0.0.7_1
libGLESv2.so keybase-desktop-3.1.2_1
libGLESv2.so wire-desktop-3.6.2885_1
libGLESv2.so Signal-Desktop-1.23.2_1
libGLESv2.so slack-desktop-3.4.2_1
```
in this case, only `libglvnd` actually ships `/usr/lib/libGLESv2.so`, the ones listed there only have this file in some non-system location, and it doesn't really look like a soname. Is this included here just to keep the linter quiet?
- this one looks ok (packages conflict)
```
libboinc_api.so.7 boinc-7.16.16_2
libboinc_api.so.7 boinc-nox-7.16.16_2
```
- etc.
next prev parent reply other threads:[~2021-04-04 23:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 2:03 [ISSUE] " gt7-void
2021-04-04 17:41 ` dkwo
2021-04-04 17:48 ` ericonr
2021-04-04 19:23 ` Duncaen
2021-04-04 19:24 ` Duncaen
2021-04-04 19:26 ` Duncaen
2021-04-04 19:26 ` Duncaen
2021-04-04 23:13 ` gt7-void
2021-04-04 23:17 ` gt7-void [this message]
2021-04-05 0:29 ` Duncaen
2021-04-05 0:29 ` Duncaen
2021-04-05 0:30 ` Duncaen
2022-05-17 2:14 ` github-actions
2022-06-01 2:14 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210404231710.sZP3qD0vBnOyt1wiJ4jQvVFtkOGY0IOli7_Rfynjx-g@z \
--to=gt7-void@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).