From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/25502] debuginfod client should default to XDG cache
Date: Tue, 18 Feb 2020 12:15:00 -0000 [thread overview]
Message-ID: <bug-25502-10460-kQ0YivBJxq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25502-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25502
--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Tom Tromey from comment #3)
> (In reply to Mark Wielaard from comment #2)
> > What about the Default database file? Currently $HOME/.debuginfod.sqlite
> >
> > Should that go under $XDG_DATA_HOME/debuginfod/ ?
> > And then probably not as hidden file?
>
> If the file can be deleted and then re-created without difficulty,
> then it should go in the cache directory as well.
It could be, if the database is gone then it can be recreated from scratch. But
it might take a lot of work depending on how many packages/dirs you want to
index.
On the other hand if the database is important it might be explicitly be given
on the command line.
Any other opinions on where the default .debuginfod.sqlite should go (and how
it should be named)?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-02-18 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:39 [Bug debuginfod/25502] New: " tromey at sourceware dot org
2020-02-06 20:46 ` [Bug debuginfod/25502] " mark at klomp dot org
2020-02-06 20:53 ` mark at klomp dot org
2020-02-07 22:37 ` tromey at sourceware dot org
2020-02-11 21:19 ` amerey at redhat dot com
2020-02-18 12:15 ` mark at klomp dot org [this message]
2020-02-18 18:18 ` amerey at redhat dot com
2020-02-18 18:52 ` tromey at sourceware dot org
2020-02-28 15:28 ` amerey at redhat dot com
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=bug-25502-10460-kQ0YivBJxq@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).