public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: mulltiib cruft: /emul
Date: Wed, 9 Aug 2006 14:57:06 +0000 (UTC)	[thread overview]
Message-ID: <ebct42$plk$5@sea.gmane.org> (raw)
In-Reply-To: 200608081143.13375.vapier@gentoo.org

Mike Frysinger <vapier@gentoo.org> posted
200608081143.13375.vapier@gentoo.org, excerpted below, on  Tue, 08 Aug
2006 11:43:13 -0400:

> looks like your mail server ate this ...
> 
> someone remind me why our emul packages install in some obscure
> directory tree rooted in /emul
> 
> if we moved these things to the standard lib32 dirs, it would certainly
> ease the pain of people doing multilib building, both in and out of
> portage
> 
> it'd also let us free up env.d crap ... but most importantly, it'll stop
> breaking my friggin tab completion for /etc

It came thru b4.  As an amd64 user, I've been hoping a member of the arch
team would reply, as it's a question that seeing it asked, I'm now curious
about myself, but nothing yet.

Pure speculation here, but the idea /might/ have been to separate prebuilt
binary stuff into /emul, so it wouldn't conflict with future multiarch
portage support (which would presumably use /lib32), which IIRC was hoped
to be here by now, but turned out to be rather complicated and had no
portage devs which had that particular itch they needed to scratch, so... 
(IOW, no blame or finger pointing, just that we'd hoped it'd be here by
2.1, and it isn't, and that's a fact amd64 continues to have to deal with.)

As I said, pure speculation, likely wrong, but that's the first logical
thing that came to my mind.  I too am interested in a real answer.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-09 15:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 15:43 [gentoo-dev] mulltiib cruft: /emul Mike Frysinger
2006-08-09 14:57 ` Duncan [this message]
2006-08-09 15:50   ` [gentoo-dev] " Mike Frysinger
2006-08-09 17:46     ` Danny van Dyk
2006-08-09 18:00     ` Richard Fish
     [not found]   ` <44DA1FBB.6060307@gentoo.org>
     [not found]     ` <1155228522.6489.97.camel@cocagne.max-t.internal>
2006-08-10 17:17       ` Donnie Berkholz
2006-08-10 17:26         ` Mike Doty
2006-08-10 19:42           ` Kevin F. Quinn
2006-08-10 20:17             ` Mike Frysinger
2006-08-11  4:24               ` Donnie Berkholz
2006-08-10 22:39           ` Chris Gianelloni
     [not found]       ` <200608101521.37851.vapier@gentoo.org>
2006-08-10 23:32         ` Doug Goldstein
2006-08-11  0:20           ` Mike Frysinger
2006-08-21 11:21 ` [gentoo-dev] " Herbie Hopkins
2006-08-21 14:29   ` Olivier Crête
2006-08-21 17:28     ` Mike Frysinger
2006-08-21 17:39       ` Olivier Crete
2006-08-21 19:08         ` Mike Frysinger
2006-08-21 20:30   ` Donnie Berkholz
2006-08-22 15:17     ` [gentoo-dev] " Duncan
2006-08-22 22:01       ` Mike Frysinger
2006-08-24 20:58   ` [gentoo-dev] " Chris Gianelloni
2006-08-25 12:26     ` Herbie Hopkins
2006-08-25 15:50       ` Chris Gianelloni

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='ebct42$plk$5@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --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