Message-ID: <50079593.3020208@users.sourceforge.net>
Date: Thu, 19 Jul 2012 00:05:23 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: cygport debug junk
References: <vl4e081f8uq3o891d33jvli21hke0q3sfk@4ax.com> <50073394.8040901@cornell.edu> <50073E51.1090709@users.sourceforge.net> <50076256.5000206@cornell.edu>
In-Reply-To: <50076256.5000206@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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

On 2012-07-18 20:26, Ken Brown wrote:
> On 7/18/2012 6:53 PM, Yaakov (Cygwin/X) wrote:
>> But again, while I can't state this as policy, you really shouldn't be
>> disabling debuginfo on a widespread or permanent basis.  It's a feature
>> and it's there for a reason.
>
> I disabled it for my recent texlive release, simply because texlive is
> so huge already that I didn't want to add to it.  Do you think that was
> the wrong decision?

Note that only the core texlive package will have debuginfo; the 
texlive-collection-* packages are just data, so there won't be debuginfo 
information anyway (and cygport only tries to make a debuginfo package 
where the debuginfo actually exists).  And while the texlive source 
package is huge, the amount of compiled code therein is a small fraction 
of that, so I don't think the debuginfo package would be really all that 
large (especially relative to the entire size of TeX).

So I'd say next time you build texlive, go ahead and enable debuginfo, 
but don't feel that you have to rebuild texlive immediately because of it.


Yaakov


--
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