Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-alt
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-alt@g.o
From: Alan Hourihane <alanh@...>
Subject: Re: moving shared libs
Date: Mon, 26 Jan 2009 17:15:55 +0000
On Fri, 2009-01-23 at 16:24 +0000, Alan Hourihane wrote:
> Seems as though AIX & FreeMiNT bump into this issue in a few ebuilds.
> 
> I've just bumped into it again with sys-libs/cracklib &
> sys-libs/e2fsprogs-libs and sys-fs/e2fsprogs.
> 
> Is it worthwhile creating a new function in the eclass directory that
> deals with these issues..
> 
> Taking sys-libs/cracklib for example, we currently have this....
> 
>         # move shared libs to /
>         dodir /$(get_libdir)
>         mv "${D}"/usr/$(get_libdir)/*.so* "${D}"/$(get_libdir)/ || die
> "could
> not move shared"
> 
> We could add (or something equivalent to with a bit of extra
> thinking)....
> 
> move_shlibs() {
>         # move shared libs to /
>         [[ $(get_libname) == ".irrelevant" ]] && return
>         dodir /$(get_libdir)
>         mv "${D}"/usr/$(get_libdir)/*.so* "${D}"/$(get_libdir)/ || die
> "could
> not move shared"
> }
> 
> and nicely change the ebuild to...
> 
>         move_shlibs
> 
> It'd really help clean up that nasty "mv" commandline I keep seeing
> everywhere in ebuilds.
> 
> Comments ?

Prefix guru's - would this be acceptable to add in the eclass ??

Alan.



References:
moving shared libs
-- Alan Hourihane
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
moving shared libs
Next by thread:
Re: moving shared libs
Previous by date:
moving shared libs
Next by date:
Re: moving shared libs


Updated Jun 17, 2009

Summary: Archive of the gentoo-alt mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.