From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] Removing .la files from x86
Date: Wed, 03 Aug 2016 08:00:00 -0000 [thread overview]
Message-ID: <20160803080043.GA7388@calimero.vinschen.de> (raw)
In-Reply-To: <c2b9aec9-fb94-7766-8e31-f5cce7ce9000@cygwin.com>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
On Aug 2 22:09, Yaakov Selkowitz wrote:
> Libtool .la files are generally a waste of time and space. They slow down
> linking of other libraries with libtool, and they cause otherwise
> unnecessary private dependencies to be pulled in by -devel packages.
> Therefore, the major distros generally remove them from their packages
> unless they are really necessary.
>
> When we first enabled Cygwin for x86_64, as we had no backwards
> compatibility to worry about, I made removing all .la files the default.
> AFAIK this has worked well, and any missing link libraries that the presence
> thereof would have masked have already been fixed.
>
> In order to do the same for x86 without breaking builds of other packages,
> AFAICS we would need a perpetual postinstall script which will continually
> remove them. The downside is that (unless the script is made a *LOT* more
> complicated) a number of -devel packages will show up as "Incomplete" until
> such time they are rebuilt with a new version of cygport.
>
> Any objections?
User confusion about incomplete packages?
What I wonder is, if cygport builds don't create/install .la files
anymore, don't we end up without them at one point anyway? Isn't it
sufficient if they go away over time?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-03 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 3:11 Yaakov Selkowitz
2016-08-03 4:16 ` Warren Young
2016-08-03 8:00 ` Corinna Vinschen [this message]
2016-08-03 9:19 ` Marco Atzeri
2016-08-03 15:58 ` Yaakov Selkowitz
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=20160803080043.GA7388@calimero.vinschen.de \
--to=corinna-cygwin@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).