From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: cygport debug junk
Date: Thu, 19 Jul 2012 17:30:00 -0000 [thread overview]
Message-ID: <bsgg08hfgd8ab4foubl0a3anhomh82lf2o@4ax.com> (raw)
In-Reply-To: <50073E51.1090709@users.sourceforge.net>
> Debuginfo is not "junk". Like most Linux binary distros, these files
> are automatically packed into a ${PN}-debuginfo package and excluded
> from other (sub)packages without further intervention by the maintainer.
> Users can then install gdb and these debuginfo packages to debug
> software in place, without having to install BRs and rebuild packages.
One disadvantage of this is that it makes the 'list' command less useful. I
used to be able to copy the output of 'cygport list' and paste it directly into
the README.Cygwin file, which is supposed to include a file listing of the
binary package. Now I have to edit the output to remove the debug files.
If the intent of 'list' is to show the contents of the binary package, then I
suggest that it automatically remove the debug files from the listing.
Thanks,
Andrew.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-19 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 20:58 Andrew Schulman
2012-07-18 22:07 ` Ken Brown
2012-07-18 22:53 ` Yaakov (Cygwin/X)
2012-07-19 1:27 ` Ken Brown
2012-07-19 5:05 ` Yaakov (Cygwin/X)
2012-07-19 14:50 ` Andrew Schulman
2012-07-19 17:30 ` Andrew Schulman [this message]
2012-07-19 21:12 ` Yaakov (Cygwin/X)
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=bsgg08hfgd8ab4foubl0a3anhomh82lf2o@4ax.com \
--to=schulman.andrew@epamail.epa.gov \
--cc=cygwin@cygwin.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).