public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: Panu Matilainen <pmatilai@redhat.com>
To: debugedit@sourceware.org
Subject: Re: Some package review feedback (bindir vs libexecdir, docs and find-debuginfo.sh naming)
Date: Thu, 6 May 2021 12:48:07 +0300	[thread overview]
Message-ID: <ba346495-d354-f706-44ed-aea287917174@redhat.com> (raw)
In-Reply-To: <c5158dee427707ddf77559e2a070f83244c8178b.camel@klomp.org>

Sorry I missed this initially, been rather hectic times for me...

On 4/30/21 3:33 PM, Mark Wielaard wrote:
> Hi,
> 
> Even though we aren't yet at debugedit 1.0 I did request a package
> review for debugedit in Fedora to see what other issues would pop up.
> 
> You can find the review here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1953633
> 
> There are two issues I think should really be resolved upstream and not
> be specific to how Fedora happens to do things.
> 
> First there is the question whether to name find-debuginfo.sh without
> the .sh extension. So the script would be named "find-debuginfo". This
> is also https://sourceware.org/bugzilla/show_bug.cgi?id=27640
> 
> I don't mind renaming the script to find-debuginfo, but then it
> wouldn't be a drop-in replacement anymore for rpm. Is that an issue?
> 
> The second issue was whether to install the executables under
> /usr/libexec/debugedit (or under /usr/lib/debugedit) instead of in the
> normal bindir. The rational given for that was that there is no
> documentation and because "normal users" would not use the executables
> directly (they might only be called by other programs (which is what
> libexec is for).

As I've said before, I personally wouldn't put this stuff into bindir, 
but then I'm not running this project :)

find-debuginfo.sh is the only thing rpm directly uses and there's 
exactly one place calling it, settable from a macro, so the exact path 
and naming doesn't matter a whole lot.

However there seem to be quite some specs referring 
/usr/lib/rpm/find-debuginfo.sh directly, so I think we'll need to 
preserve /usr/lib/rpm/find-debuginfo.sh path by planting a symlink to 
the real thing there (or a wrapper script if necessary). Not a big deal, 
I'll handle this from rpm.

> 
> To fix the documentation issue I submitted patches to make sure
> everything has at least a man page. I think these programs might be
> used as is by normal users. Although find-debuginfo.sh needs to stop
> depending on RPM_environment variables. So IMHO bindir is the more
> natural place to install them.

If you prefer bindir then by all means go with it.

	- Panu -

> For a 1.0 release we should make sure the documentation patches are
> there. And fix the RPM_environment variables issue:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27637
> 
> Please let me know what you think of the above issues and whether there
> are any other issues that you think should be resolved before we do a
> 1.0 release.
> 
> Thanks,
> 
> Mark
> 


      parent reply	other threads:[~2021-05-06  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 12:33 Mark Wielaard
2021-05-05 22:59 ` Mark Wielaard
2021-05-06  9:48 ` Panu Matilainen [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=ba346495-d354-f706-44ed-aea287917174@redhat.com \
    --to=pmatilai@redhat.com \
    --cc=debugedit@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).