From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: PATCH: PR27783: debuginfod: fetch default DEBUGINFOD_URLS from systemwide file
Date: Wed, 5 May 2021 16:41:04 +0200 [thread overview]
Message-ID: <20210505144104.GG3245@wildebeest.org> (raw)
In-Reply-To: <20210503130542.GB2105@redhat.com>
Hi Frank,
On Mon, May 03, 2021 at 09:05:42AM -0400, Frank Ch. Eigler via Elfutils-devel wrote:
> > [...] But I think that is the nice things about using the
> > environment variable to indicate debuginfod-client should be used in
> > a specific environment. [...]
>
> This is only a way of making the default more of an opt-out than an
> opt-in, and put it into a -single- systemwide spot (instead of two
> profile.* files plus all the opt-in systemd unit files). A daemon
> -disinterested- in participating could set the same env var to be an
> empty string.
But I think an interactive user environment is different from a
standalone running daemon environment. So I think it makes sense they
might use diffent opt-in/out strategies.
> > Also some distros already seem to rely on the profile files, so
> > removing them now seems like a bad idea.
>
> Well, nothing stops them from continuing to ship the same files, they
> don't need to come from elfutils upstream.
>
> Anyway all that said, I'm neutral on this change. Any other opinions?
It is really a distro decission I guess. How do different distros
handle this?
Cheers,
Mark
prev parent reply other threads:[~2021-05-05 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 16:13 Frank Ch. Eigler
2021-05-03 12:59 ` Mark Wielaard
2021-05-03 13:05 ` Frank Ch. Eigler
2021-05-05 14:41 ` Mark Wielaard [this message]
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=20210505144104.GG3245@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).