public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] multilib clean up
Date: Mon, 7 Mar 2011 05:24:29 -0500	[thread overview]
Message-ID: <AANLkTim=gsAt6YCX9wk_1cg9acY3TYbbun693xzEhvC7@mail.gmail.com> (raw)

i plan on punting these (hardly used) functions from the
multilib.eclass (once the handful of open bugs are closed):
  get_ml_incdir
  prep_ml_includes
  create_ml_includes
  create_ml_includes-absolute
  create_ml_includes-tidy_path
  create_ml_includes-listdirs
  create_ml_includes-makedestdirs
  create_ml_includes-allfiles
  create_ml_includes-sym_for_dir
further, the CDEFINE_xxx multilib vars will go with them

for the most part, these were really only used by the glibc ebuilds.
for the ones that dont support multilib natively (and necessitated
these funcs in the first place), i'll simply punt the ebuilds.  this
will probably be just the glibc-2.5 ebuilds for now.

also, i'll be converting the glibc ebuilds do always invoke the
multilib_env helper functions.  this will allow us to drop the
{C,LD}FLAGS_xxx and friends from profiles since glibc was the main
consumer.  i imagine this inadvertently break some other packages, so
if people want to test this on their own systems before i make the
commit, that'd be cool.  the plan would be for said breakage will go
through bugzilla to get the ebuild updated rather than reverting the
profile.
-mike



             reply	other threads:[~2011-03-07 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 10:24 Mike Frysinger [this message]
2011-03-07 17:35 ` [gentoo-dev] multilib clean up Thomas Sachau
2011-03-07 22:29   ` Mike Frysinger
2011-03-16 20:08 ` [gentoo-dev] " Mike Frysinger
2011-03-18 19:46 ` Mike Frysinger
2011-03-18 22:08 ` Mike Frysinger

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='AANLkTim=gsAt6YCX9wk_1cg9acY3TYbbun693xzEhvC7@mail.gmail.com' \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@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