The client automatically tries to resolve package dependencies on Gentoo. This is a good thing, but it should not record that dependencies to the world file. The client is just a temporary download (check out git, get certificate, remove the client) and threfore should not be treated as a regular installation. especially the package management does not know about a possible remove the client and therefore some garbage remains on the system. Furthermore, it is not possible to see if the packages were contained in world before the call of letsencrypt-auto. Therefore, the manual removal is also error prone (one might remove something one actuallly needs, but have forgotten about).
proposed solution:
install the packages with the --oneshot option and ask the user if he wants to proceed (–ask --verbose) before actually starting the installation of packages.
Example of current behavior:
wgs-vm2 letsencrypt ## ./letsencrypt-auto --help
WARNING: Gentoo support is very experimental at present…
if you would like to work on improving it, please ensure you have backups
and then run this script again with the --debug flag!
wgs-vm2 letsencrypt # ./letsencrypt-auto --debug --help
Bootstrapping dependencies for Gentoo…
Calculating dependencies… done!
>>> Recording app-misc/ca-certificates in “world” favorites file…
>>> Recording dev-lang/python:2.7 in “world” favorites file…
>>> Recording dev-libs/libffi in “world” favorites file…
>>> Recording dev-libs/openssl in “world” favorites file…
>>> Recording virtual/pkgconfig in “world” favorites file…
>>> Verifying ebuild manifests
>>> Emerging (1 of 4) app-doc/NaturalDocs-1.52-r1::gentoo
>>> Emerging (2 of 4) dev-python/virtualenv-13.1.2::gentoo
>>> Emerging (3 of 4) dev-util/dialog-1.2.20150920::gentoo
…
…