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

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]

Re: [arch-general] [arch-dev-public] Finishing the /usr move

2013-05-29 Thread Paul Gideon Dann
On Wednesday 29 May 2013 10:39:45 Gaetan Bisson wrote: > This has been discussed many times in the past. All you had to do was > make a simple search before putting your question to this list... > > https://encrypted.google.com/search?q=archlinux+/usr/bin+move My apologies, and thanks for t

Re: [arch-general] [arch-dev-public] Finishing the /usr move

2013-05-29 Thread Gaetan Bisson
[2013-05-29 09:30:18 +0100] Paul Gideon Dann: > On Wednesday 29 May 2013 18:13:01 Allan McRae wrote: > > Yes - /sbin, /usr/sbin and /bin will all point at /usr/bin. So > > hardcoded paths will not matter. Only file locations will. > > Just a little curious: does someone know what the reason is

Re: [arch-general] [arch-dev-public] Finishing the /usr move

2013-05-29 Thread Paul Gideon Dann
On Wednesday 29 May 2013 18:13:01 Allan McRae wrote: > Yes - /sbin, /usr/sbin and /bin will all point at /usr/bin. So > hardcoded paths will not matter. Only file locations will. Just a little curious: does someone know what the reason is that we're moving everything to /usr/bin instead of /bi