From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 13-11-2012
Date: Thu, 8 Nov 2012 14:07:23 -0300 [thread overview]
Message-ID: <20121108140723.01ec3444@gentoo.org> (raw)
In-Reply-To: <20121030163820.GA7141@linux1>
On Tue, 30 Oct 2012 11:38:20 -0500
William Hubbs <williamh@gentoo.org> wrote:
[...]
> > The end result of this assumption is that the use of
> > gen_usr_ldscript() and the move of libs from /usr/lib to /lib will
> > become deprecated, correct? I think it's pertinent to note this (or
> > whatever other changes will then be requested/required for Council
> > to decide on) within this discussion, if not also within the
> > "plan"..
>
> On Linux, yes, you are correct. I wouldn't propose touching it for the
> *bsd platforms.
>
> Also, once everyone switches over, this deprecation would be
> transparent. The calls to gen_usr_ldscript would be removed from
> ebuilds where possible, and the function itself could be disabled on
> linux. Once this is done, when packages are rebuilt, the libraries
> would migrate back to /usr/lib.
(I hadn't seen that thread.)
Removing it from ebuilds implies touching it for *bsd platforms. A lot
of ebuilds are shared between the g/*bsd and g/linux port, that's
somewhat the point of the whole thing. Of course, there may be
linux-only packages where the calls to gen_usr_ldscript will become
useless, but in general these calls should remain and the function
shall be a no-op on platforms where this is desired.
next prev parent reply other threads:[~2012-11-08 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 15:00 [gentoo-project] Call for agenda items -- Council meeting 13-11-2012 Fabian Groffen
2012-10-30 15:36 ` William Hubbs
2012-10-30 16:21 ` Ian Stakenvicius
2012-10-30 16:38 ` William Hubbs
2012-11-02 17:22 ` William Hubbs
2012-11-08 17:07 ` Alexis Ballier [this message]
2012-11-08 17:38 ` William Hubbs
2012-10-30 22:06 ` Chí-Thanh Christopher Nguyễn
2012-10-30 22:09 ` Ciaran McCreesh
2012-10-30 22:11 ` Chí-Thanh Christopher Nguyễn
2012-10-30 22:34 ` Zac Medico
2012-10-31 6:41 ` Pacho Ramos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121108140723.01ec3444@gentoo.org \
--to=aballier@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox