From: pudiva <pudiva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: sane-airscan-0.99.24
Date: Thu, 25 Mar 2021 15:42:26 +0100 [thread overview]
Message-ID: <20210325144226.8UBPYV46NdWxazs_ff7OWfdzYf7dfXhxGVXlRk7aOjo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29627@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
New comment by pudiva on void-packages repository
https://github.com/void-linux/void-packages/pull/29627#issuecomment-806875028
Comment:
> Maybe report it upstream, but the makefile version is missing the unversioned symlink:
>
> > /usr/lib/sane/libsane-airscan.so -> /usr/lib/sane/libsane-airscan.so.1
I submitted a PR, but upstream didn't like the unversioned symlink, and also shared that they don't really maintain the **meson** build, but just try to not break it ~ sounds like they prefer **make**. Their full response:
> Nobody links against these drivers directly, they are always loaded via sane-dll, which doesn't use unversioned symlink. So I believe that SANE itself creates these links only for legacy reasons and there is no need to reproduce this behaviour in the independent package.
>
> Official packages for Fedora, Debian and Ubuntu come without this symlink and it causes no problems and no complains.
>
> Regarding meson build, it was contributed by my users and I don't maintain it, I only keep it here for everybody's convenience and trying not to break when something changes in the project.
>
> So really thank for your contribution, but in this particular case I don't think we really need it.
https://github.com/alexpevzner/sane-airscan/pull/132#issuecomment-806477624
next prev parent reply other threads:[~2021-03-25 14:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 13:13 [PR PATCH] " pudiva
2021-03-20 13:15 ` [PR PATCH] [Updated] " pudiva
2021-03-20 13:35 ` ericonr
2021-03-22 7:54 ` oynqr
2021-03-22 14:57 ` [PR PATCH] [Updated] " pudiva
2021-03-22 15:11 ` pudiva
2021-03-22 15:56 ` [PR REVIEW] " ericonr
2021-03-22 15:58 ` ericonr
2021-03-22 22:27 ` [PR REVIEW] " pudiva
2021-03-22 22:28 ` [PR PATCH] [Updated] " pudiva
2021-03-22 22:34 ` pudiva
2021-03-22 22:52 ` pudiva
2021-03-25 14:42 ` pudiva [this message]
2021-03-25 16:56 ` [PR REVIEW] " pudiva
2021-03-25 20:59 ` ericonr
2021-03-25 21:00 ` ericonr
2021-03-25 21:01 ` [PR REVIEW] " ericonr
2021-03-25 21:01 ` ericonr
2021-03-25 21:02 ` ericonr
2021-03-25 22:08 ` pudiva
2021-03-25 22:09 ` pudiva
2021-03-25 22:11 ` [PR PATCH] [Updated] " pudiva
2021-03-25 22:25 ` [PR REVIEW] " pudiva
2021-03-26 1:03 ` ericonr
2021-03-26 1:06 ` ericonr
2021-03-26 1:06 ` ericonr
2021-03-26 1:37 ` [PR PATCH] [Updated] " pudiva
2021-03-26 1:37 ` [PR REVIEW] " pudiva
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 10:15 [PR PATCH] " oynqr
2021-03-26 1:07 ` ericonr
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=20210325144226.8UBPYV46NdWxazs_ff7OWfdzYf7dfXhxGVXlRk7aOjo@z \
--to=pudiva@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).