=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 24 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 13 fully signed off packages
* 68 packages missing signoffs
* 9 packages older than 14 days
Our packages in our repos by default don't need static libraries
(random .a files all around). I think they are a waste of disc space
and abuse bandwidth when uploading/mirroring packages. Most users will
never need them.
I suggest to drop all static libs by creating a ToDo list and install a
On 02/03/13 19:16, Andreas Radke wrote:
Our packages in our repos by default don't need static libraries
(random .a files all around). I think they are a waste of disc space
and abuse bandwidth when uploading/mirroring packages. Most users will
never need them.
I suggest to drop all static
Am Sat, 02 Mar 2013 19:29:13 +1000
schrieb Allan McRae al...@archlinux.org:
Just add *.a to PURGE_TARGETS in makepkg.conf rather than manually
removing them. Anyone who needs them can disable that.
(I will keep them in glibc/gcc/binutils...)
Allan
Nice solution. We should add *.a to
Hi,
Note that one of the two most popular Go compilers relies on static
compilation and .a files:
pacman -Ql go | grep \.a$ | wc -l
261
Go was created by some of the same people that created Plan9, so I
assume the choice of using static compilation is inspired by that:
as long as there is a simple way to turn off purging static libs, thiz
sounds good
Note that haskell also uses static libs
On 02/03/13 12:10, Thomas Dziedzic wrote:
as long as there is a simple way to turn off purging static libs, thiz
sounds good
Note that haskell also uses static libs
Can't we add a rule to namcap, which warns packagers about static libs?
Then the packager can decide whether they should
On Sat, Mar 2, 2013 at 10:16 AM, Andreas Radke andy...@archlinux.org wrote:
Our packages in our repos by default don't need static libraries
(random .a files all around). I think they are a waste of disc space
and abuse bandwidth when uploading/mirroring packages. Most users will
never need
On Sat, Mar 02, 2013 at 01:32:48PM -0300, Thiago Kenji Okada wrote:
nss-pam-ldapd is actively maintained while nss_ldap/pam_ldap are not
updated in a while. nss-pam-ldapd is more robust too (I had a similar
problem like https://bugs.archlinux.org/task/33672 that didn't occur with
On Sat, Mar 02, 2013 at 04:13:01PM -0500, Dave Reisner wrote:
On Sat, Mar 02, 2013 at 01:32:48PM -0300, Thiago Kenji Okada wrote:
nss-pam-ldapd is actively maintained while nss_ldap/pam_ldap are not
updated in a while. nss-pam-ldapd is more robust too (I had a similar
problem like
Le 2013-03-02 05:14, Andreas Radke a écrit :
Am Sat, 02 Mar 2013 19:29:13 +1000
schrieb Allan McRae al...@archlinux.org:
Just add *.a to PURGE_TARGETS in makepkg.conf rather than manually
removing them. Anyone who needs them can disable that.
(I will keep them in glibc/gcc/binutils...)
On Thu, Feb 14, 2013 at 12:38 AM, Sébastien Luttringer se...@seblu.net wrote:
On Fri, Feb 8, 2013 at 1:23 AM, Sébastien Luttringer se...@seblu.net wrote:
...
Some news from the front:
- Wayland is in extra, thanks to Tom G. for moving it.
- Mesa and cairo have their wayland backend enabled
[2013-03-02 15:17:02 +0100] Jelle van der Waa:
Can't we add a rule to namcap, which warns packagers about static libs?
Then the packager can decide whether they should included or removed.
Most packagers would not notice or care enough to remove static libs
from the many packages where they are
13 matches
Mail list logo
