From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] cygport: split debuginfo packages
Date: Tue, 17 Jul 2012 19:55:00 -0000 [thread overview]
Message-ID: <20120717195503.GA2849@ednor.casa.cgf.cx> (raw)
In-Reply-To: <87txx6w4mo.fsf@Rainer.invalid>
On Tue, Jul 17, 2012 at 09:48:31PM +0200, Achim Gratz wrote:
>Christopher Faylor writes:
>> Maybe the .debuginfo files should be in a "Debug" category.
>
>I don't think that would be the right thing to do. It would only be of
>help if the debuginfo packages were not shown in the other categories
>together with the installation packages, but a flat Debug category seems
>even less appealing. It should be possible to get the debuginfo for
>"this package" directly from the package selection, not rummaging around
>in the Debug category trying to find something that looks like it might
>be related to "that package".
Ok, let me put it this way. I'm not keenly interested in spending time
updating setup.exe and the setup.ini generation tools for special case
handling of debuginfo.
Maybe that helps clarify things.
cgf
next prev parent reply other threads:[~2012-07-17 19:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 6:24 Yaakov (Cygwin/X)
2012-06-21 9:03 ` Corinna Vinschen
2012-06-21 9:35 ` Corinna Vinschen
2012-06-21 19:47 ` Yaakov (Cygwin/X)
2012-06-22 9:51 ` Corinna Vinschen
2012-06-21 12:56 ` Christopher Faylor
2012-06-21 14:22 ` Jon TURNEY
2012-06-21 16:10 ` Christopher Faylor
2012-06-22 15:23 ` Ken Brown
2012-06-29 19:48 ` Yaakov (Cygwin/X)
2012-06-30 16:49 ` Ken Brown
2012-07-07 13:11 ` Jon TURNEY
2015-02-23 12:15 ` Jon TURNEY
2015-02-27 6:27 ` Yaakov Selkowitz
2015-03-01 17:54 ` Jon TURNEY
2015-03-01 19:25 ` Yaakov Selkowitz
2015-03-09 12:55 ` Jon TURNEY
2012-07-17 18:37 ` Achim Gratz
2012-07-17 18:39 ` Christopher Faylor
2012-07-17 19:48 ` Achim Gratz
2012-07-17 19:55 ` Christopher Faylor [this message]
2012-07-17 20:25 ` 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=20120717195503.GA2849@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-apps@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).