From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-June/005386.html | 153 +++++++++++++++++++++++++++++++ 1 file changed, 153 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/005386.html (limited to 'zarb-ml/mageia-dev/2011-June/005386.html') diff --git a/zarb-ml/mageia-dev/2011-June/005386.html b/zarb-ml/mageia-dev/2011-June/005386.html new file mode 100644 index 000000000..c0cfce28a --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005386.html @@ -0,0 +1,153 @@ + + + + [Mageia-dev] [RFC] Removing .la files + + + + + + + + + +

[Mageia-dev] [RFC] Removing .la files

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Fri Jun 10 20:23:04 CEST 2011 +

+
+ +
On Fri, 10 Jun 2011, Colin Guthrie wrote:
+
+> 'Twas brillig, and Christiaan Welvaart at 10/06/11 16:34 did gyre and
+> gimble:
+
+>> If people are using a system with
+>> gnome installed to develop gnome, it's not strange they run into
+>> problems.
+>
+> I call shenanigans. I do this kind of stuff all the time. It's easy to
+> use a custom prefix (i.e. not /usr) if you select the right configure
+> options. It means you get a working system but can also develop the next
+> version. I've been doing this kind of stuff for years. The removal of
+> the .la files will make this approach much easier.
+
+Let's make one thing clear, however. These .la files are not created or 
+installed by packagers, but rather by the build system of (in this case) 
+gnome libraries. And maybe you are quite happy with the absolute paths 
+in the .la files in your buildroot/prefix.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1