To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
Subject: Re: cygport debug junk
Date: Thu, 19 Jul 2012 13:29:49 -0400
Lines: 16
Message-ID: <bsgg08hfgd8ab4foubl0a3anhomh82lf2o@4ax.com>
References: <vl4e081f8uq3o891d33jvli21hke0q3sfk@4ax.com> <50073394.8040901@cornell.edu> <50073E51.1090709@users.sourceforge.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> 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