Macro names have changed, devs should have the newest version of autoconf-archive possible available to them.
Created attachment 218965 [details] autoconf-archive-2009.12.16.ebuild There are changes in SRC_URI and in the buildsystem. For example, texinfos are installed instead of HTML documentation. Both of these changes much simplify this ebuild.
Heh, this package does not have maintainer at the moment. But it looks simple, I'll review/check and bump. Thank you for report Nathan.
Fixed. Nathan, note that in gentoo we install documentation into /usr/share/doc/${PF} instead or /usr/share/doc/${PN}. That's why I took previous ebuild as a starting point.
Created attachment 218999 [details] autoconf-archive-2009.12.16-docs.txt I removed the docdir-moving magic because I was convinced that autoconf-archive had stopped installing all docs. Now I see that it installs some docs, which confuses me. However, I would like to note these two things concerning the docdir. See that at least one of these files is duplicated by the output from this attached shell session. Also, I am quite sure that autoconf-archive's configure script does honor the --docdir option. Now I discover that it doesn't use the information from --docdir and instead uses $(pkgdatadir) which is unsettable at ./configure time. Maybe an ``rm -f'' rather than ``mv'' or a sed -i -e '/dist_pkgdata_DATA/d' Makefile.in || die during src_prepare() would be better?
Oh, the actual problem with multiple copies of the docs is showing up because you expect /usr/share/doc/${PF} not to exist when you wrote your ``mv'' command. Since I am using portage-multilib, this means that src_install() gets run twice and you end up moving a second copy of the folder into itself. Another side effect of using mv instead of dodoc is that these files aren't being compressed like all other doc files.
> Since I am using portage-multilib, this means that src_install() gets > run twice and you end up moving a second copy of the folder into itself. This should be reported to portage-multilib developers. Probably portage-multilib should clean image directory every time switching on new libapi and after all merge this image directories together. That said I've wrote ebuild a bit differently as I don't like it install COPYING file.
