With a blank LIBPATHENV the ruby build tools fall back to using LD_PRELOAD
to load libruby.so during the build process. With uclibc, preloading is
now optional and not enabled at least in the vanilla stage3 that we
produce. This causes the build to fail since there are no options left
to find libruby.so.
Fixed by adding ${S} to the temporary LD_LIBRARY_PATH during the install
phase. Thanks to blueness for the original patch.
Fixes bug 564272
Package-Manager: portage-2.2.28
We had a few users request to proxy-maintain this package. Now that
its open bugs are fixed, this commit adds two of those users (Philippe
Chaintreuil and Marcin Mirosław) to metadata.xml. The Proxy
Maintainers project has been added to support them.
I've added myself, too, for now, so that I will be CCed on bugs
arising from my recent changes.
Gentoo-Bug: 583908
Package-Manager: portage-2.2.28
To make life easier for our users, a cron job that runs sa-update
nightly has been provided. It is only installed with USE=cron, but an
elog will mention its existence when that USE flag is disabled. The
cron job will also attempt to restart or reload spamd/amavisd if the
signatures have been updated.
Alongside that new feature, some of the dependencies have been cleaned
up. Pointless version bounds were removed, and an obsolete perl module
or two was pruned. The libwww-perl dependency was replaced by
wget/curl.
Gentoo-Bug: 532094
Package-Manager: portage-2.2.28
Upstream has dropped this configure option in favor of the -D runtime
flag (see upstream commit 9951518076582e4d490aca3fbdc9cb8c965fca38).
There's no need to keep it in the ebuild, and it causes build failures.
Apparently, I misread the dependencees and added the dependence on typing that
should have been a blocker. This commit rectifies that situation. I'm not
convinced other problems don't exist and we may see more bugs before this is
completely resolved.
Package-Manager: portage-2.3.0_rc1
mgorny had the right idea in e4333453, but EAPI 1 does not execute
src_configure.
Bug: https://bugs.gentoo.org/582206
Package-Manager: portage-2.3.0_rc1_p14
Also remove .pydistutils.cfg from HOME before returning.
This config should only be needed when we are invoking setup.py. The
esetup.py wrapper provides a normalized way for doing this; if ebuilds
call setup.py without the wrapper, they are now also responsible for
setting the build directory if necessary.
This change allows us to stop overriding the HOME variable, and prevents
leakage of eclass-specifc configuration to the general ebuild
environment.
