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

2013-05-29 Thread Tom Gundersen 
On Wed, May 29, 2013 at 3:31 AM, Allan McRae al...@archlinux.org 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?

Sounds like a reasonable default. +1 from me.

-t

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

2013-05-29 Thread Andreas Radke 
Am Wed, 29 May 2013 10:03:29 +0200
schrieb Gaetan Bisson bis...@archlinux.org:


 I doubt most of the static libraries our packages ship ever get used,
 so I strongly support getting rid of all that dead weight (that's
 115M on my system, for instance). If needed, we can explicitly re-add
 options=('staticlibs') to core libraries' PKGBUILD, but that should
 really be the exception rather than the rule.
 
 Cheers.
 

+1

-A


signature.asc
Description: PGP signature

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

2013-05-29 Thread Pierre Schmitz 
Am 29.05.2013 03:31, schrieb Allan McRae:
 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.html

Let me know when you commit this to pacman. I can then adjust devtools
as we use our own copy of makepkg.conf here.

-- 
Pierre Schmitz, https://pierre-schmitz.com

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

2013-05-29 Thread Eric Bélanger 
On Tue, May 28, 2013 at 9:31 PM, Allan McRae al...@archlinux.org 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



No objections here.

Eric


 [1]

 https://mailman.archlinux.org/pipermail/arch-dev-public/2013-March/024552.html

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

2013-05-29 Thread Allan McRae 
On 30/05/13 02:31, Pierre Schmitz wrote:
 Am 29.05.2013 03:31, schrieb Allan McRae:
 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.html
 
 Let me know when you commit this to pacman. I can then adjust devtools
 as we use our own copy of makepkg.conf here.
 

I will do it with the pacman-4.1.2 update.

Allan

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

2013-05-28 Thread Allan McRae 
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.html

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

2013-05-28 Thread Thomas Dziedzic 
On Tue, May 28, 2013 at 6:31 PM, Allan McRae al...@archlinux.org 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?


I have no personal issues with this move.
But just to let everybody know, we will need to add options=(staticlibs) to
all haskell packages since haskell primarily uses static libs.