Re: [arch-general] [arch-dev-public] Adding !staticlibs to our default makepkg.conf

2013-05-29 Thread Hussam Al-Tayeb
On Wednesday 29 May 2013 11:31:11 Allan McRae wrote:
 We discussed removing static libraries for most packages back in March [1].
 
 Now makepkg for pacman-4.1 has an option staticlibs that automatically
 removes them. Should I make that the default in our makepkg.conf?
 
 Allan
 
 
 [1]
 https://mailman.archlinux.org/pipermail/arch-dev-public/2013-March/024552.ht
 ml

Why not check first which applications build with --disable-static?
A few packages like libpng, etc.. can be compiled with --disable-static which 
feels like a more neat approach then deleting the static libraries.


Re: [arch-general] [arch-dev-public] Adding !staticlibs to our default makepkg.conf

2013-05-29 Thread Gaetan Bisson
[2013-05-29 20:24:14 +0300] Hussam Al-Tayeb:
 Why not check first which applications build with --disable-static?

99% of all applications use autotools and therefore support this.

Now do you really feel like adding an extra line to every PKGBUILD in
our repository is neater than just enabling an option in makepkg.conf?!?

-- 
Gaetan