Re: [gentoo-dev] hardcoding lib in ebuilds, and using econf without einstall

["Michael Sterrett -Mr. Bones.-" <msterret@coat.com>]

On Thu, 19 Aug 2004, Travis Tilley wrote:

> problem #3) since econf might set libdir now, it's no longer sane to not set
> libdir during make install, either by setting it in the ebuild or by using
> einstall. ebuilds that use econf will have --libdir=/usr/${CONF_LIBDIR} when [
> -z "${CONF_LIBDIR}" ] (this change is in the ebuild.sh in >= portage
> 2.0.51_pre18), so make install will try to install the libraries to the live
> filesystem if einstall isnt also used.

No, einstall is not the preferred method.

    make DESTDIR="${D}" install || die "make install failed"

is the preferred method.  That should work fine for Makefiles that aren't
broken with regard to DESTDIR.  If the Makefiles *are* broken, the best
thing to do is to fix them and submit a patch upstream.  If that's not
done, *then* falling back to einstall is fine, but that shouldn't be the
first choice.

Michael Sterrett
  -Mr. Bones.-
mr_bones_@gentoo.org

--
gentoo-dev@gentoo.org mailing list