X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: cygport debug junk Date: Thu, 19 Jul 2012 13:29:49 -0400 Lines: 16 Message-ID: References: <50073394 DOT 8040901 AT cornell DOT edu> <50073E51 DOT 1090709 AT users DOT sourceforge DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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