X-Spam-Check-By: sourceware.org
Message-ID: <4556B8B2.2090303@users.sourceforge.net>
Date: Sun, 12 Nov 2006 00:01:22 -0600
From: "Yaakov S (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [Packaging bug] Re: [ANNOUNCEMENT] Updated: fontconfig-2.4.1-1
References: <announce DOT 87r6ww3gfm DOT fsf AT peder DOT flower> 	<824ptrpc1s DOT fsf AT vzell-de DOT de DOT oracle DOT com> <87irhnsi2k DOT fsf AT peder DOT flower>
In-Reply-To: <87irhnsi2k.fsf@peder.flower>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jan Nieuwenhuizen wrote:
> The .la files are needed at runtime if client code uses libtool's
> libltdl's dlopen'ing to access the shared library.
> 
> For example, try readline activation code in guile without it's .la
> or try dlopening fontconfig, ftm

According to this argument, every library should include it's .la.
Nevertheless, the precedent in all the distros is that .la belongs in
- -devel packages, because it's primary purpose is for libtool linking;
not that much actually uses libltdl after all.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFVrixpiWmPGlmQSMRApWbAKDkNMvD9IEVx6ZulfByopPBGUZQPQCfWVrv
DRhlux8cEp4rCYBxv9D6LD0=
=4rJd
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/