From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RFC: avahi-stub possible?
Date: Fri, 29 May 2020 11:27:58 +0200 [thread overview]
Message-ID: <20200529092758.ne6Vn44vv6nly9mVghzylHt2IqCoLDL2UGZ5_5uFhfg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22389@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/22389#issuecomment-635873529
Comment:
@Chocimier this is of course possible. It requires additional effort on the side of the maintainer or anyone from the team. In case of e.g. `pulseaudio` or `cups` I'm not sure that separating avahi dependent submodules from the rest is possible.
@ericonr yes, we would have to write such a project. We would basically have a *fork* of avahi with all functionality stripped away and functions just forwarding to the real thing, if it was found, otherwise returning an error condition. I haven't seen something like this already being developed.
I would try to do that for avahi. I've done similar things with Windows DLLs e.g. to intercept all TWAIN API calls and log and debug them, so in theory I would know what to do. What I'm asking here is if someone sees elementary reasons why this would not work.
next prev parent reply other threads:[~2020-05-29 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 20:20 [ISSUE] " pullmoll
2020-05-28 23:19 ` Chocimier
2020-05-28 23:46 ` ericonr
2020-05-29 9:27 ` pullmoll [this message]
2020-05-29 9:47 ` Chocimier
2020-05-29 10:13 ` pullmoll
2020-05-29 12:08 ` Johnnynator
2020-05-30 2:31 ` ahesford
2020-05-31 15:39 ` [ISSUE] [CLOSED] " pullmoll
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=20200529092758.ne6Vn44vv6nly9mVghzylHt2IqCoLDL2UGZ5_5uFhfg@z \
--to=pullmoll@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).