public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Martin Liška" <mliska@suse.cz>, debugedit@sourceware.org
Subject: Re: [PATCH] Add --dwz-single-file-mode argument for find-debuginfo.sh.
Date: Tue, 23 Mar 2021 15:50:23 +0100	[thread overview]
Message-ID: <73cf124bdde70886084ef946f197c4d914a1cf9d.camel@klomp.org> (raw)
In-Reply-To: <1bab6d9a-67d3-3ec1-af8e-d002cd1508d4@suse.cz>

Hi Martin,

On Tue, 2021-03-23 at 15:09 +0100, Martin Liška wrote:
> Sometime it's handy to disable multi-file mode and the patch
> adds option for that: --dwz-single-file-mode.
> 
> It will be used in openSUSE for packages that use baselibs.conf
> mechanism.
> 
> The patch was already approved in rpm pull request:
> https://github.com/rpm-software-management/rpm/pull/1579
> 
> Signed-off-by: Martin Liska <mliska@suse.cz>

The patch didn't fully translate from the rpm git repo to the debugedit
repo, but I figured out how to apply it anyway. I added a "dwz (1)" to
the documentation for -m.

It seems a useful option, so I pushed it.

I think if you do/set this then you can simply not create the .dwz
directory (which would later be removed because empty) and you could in
theory run the dwz instances in parallel with separate dwz invocations.

But note that find-debuginfo.sh isn't fully integrated yet into
debugedit. It still contains various dependencies on rpm, see 
https://sourceware.org/bugzilla/show_bug.cgi?id=27637 it doesn't have
proper --usage/help support and it doesn't have a testsuite yet.

Cheers,

Mark

      reply	other threads:[~2021-03-23 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 14:09 Martin Liška
2021-03-23 14:50 ` 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=73cf124bdde70886084ef946f197c4d914a1cf9d.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=debugedit@sourceware.org \
    --cc=mliska@suse.cz \
    /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).