[arch-dev-public] Punishment needed for not building in a chroot
allan at archlinux.org
Sun Dec 6 17:53:25 EST 2009
We have been through this many times... you should always build in a
clean chroot. But there are continuously bugs about packages linking to
non-deps. We should never have such bugs.
> readelf -d /usr/bin/mpd
0x00000001 (NEEDED) Shared library: [libjack.so.0]
> pactree -u mpd | sort
How did that get to linking to jack without jack being in its dependency
tree? Poor packaging...
The tools are very simple to use and are described in the wiki
There is _no_ excuse not to use them. The are minor changes needed for
doing i686 builds on x86_64 and vise versa, but there are plenty of us
doing that so help is available. Ask for help if needed.
So, we need a creative punishment for those that causes bugs by not
building in a clean chroot. It is too early in the morning for me to be
creative so I am struggling to come up with ideas besides beatings and
removal of commit privileges. Any better ideas?
More information about the arch-dev-public