public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Olivier Crete <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mulltiib cruft: /emul
Date: Mon, 21 Aug 2006 13:39:40 -0400	[thread overview]
Message-ID: <1156181980.2497.3.camel@cocagne.max-t.internal> (raw)
In-Reply-To: <200608211328.37602.vapier@gentoo.org>

On Mon, 2006-21-08 at 13:28 -0400, Mike Frysinger wrote:
> On Monday 21 August 2006 10:29, Olivier Crête wrote:
> > On Mon, 2006-21-08 at 12:21 +0100, Herbie Hopkins wrote:
> > > I've always viewed the emul libs as a temporary measure until we had full
> > > multilib fuctionality in portage. Afaik the only person working on this
> > > was eradicator who has been mia for a while now so I'm unsure weather
> > > this is ever likely to arise. Given that it looks like we'll be stuck
> > > with these binary libs for some time yet then we may as well do as you
> > > suggest and install them in a standard location to make building against
> > > them a bit easier. I'll look into doing this when I next version bump the
> > > packages.
> >
> > I still believe we should reserve the regular directory for the real
> > multilib stuff, otherwise it will be very painful when we decide to
> > move. And continue to put the stopgap binary packages in /emul.
> 
> why ?  this is what blockers are for

Will we make emul-x86-gtk-libs block gtk+? We dont have use based
deps/blockers... how long will it take before we have API/arch based
ones. In my humble opinion, keeping that stuff in emul is much better,
in the same way as we would install binary packages in /opt and
not /usr.

-- 
Olivier Crête
tester@gentoo.org
Gentoo Developer


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-21 17:42 UTC|newest]

Thread overview: 25+ 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 ` [gentoo-dev] " Duncan
2006-08-09 15:50   ` 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-08-08  3:31 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=1156181980.2497.3.camel@cocagne.max-t.internal \
    --to=tester@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