public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: m h <sesquile@gmail.com>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Re: Attempt to use prefix on linux as secondary...
Date: Fri, 16 Dec 2005 11:10:17 -0800	[thread overview]
Message-ID: <e36b84ee0512161110hb2dc0d5ga3b334fe3fc27d77@mail.gmail.com> (raw)
In-Reply-To: <20051216121831.GF30053@nightcrawler.e-centre.net>

Brian -
Thanks for chiming in here.  And thanks for your efforts. (I was able
to meet Seemant in India two weeks ago, and he couldn't say enough
good about you).

On 12/16/05, Brian Harring <ferringb@gentoo.org> wrote:
> On Thu, Dec 15, 2005 at 05:51:26PM -0800, m h wrote:
> > While I'm firing off questions, any hints as to why there are no
> > ebuilds to satisfy bash?  (I'm starting through the depgraph code, but
> > it is hairy and ugly....)
> prefix portage _only_ allows using EAPI="prefix" ebuilds right now.
>
> Down the line, if prefix is approved/integrated, then an actual EAPI
> release will be used instead of the fake one created.
>
> Either way, why there are no ebuilds is due to portage automatically
> filtering out all ebuilds that lack a matching EAPI.
>
> It's a protection feature, if portage doesn't know of that EAPI level,
> it won't allow the user to use it.

As far as I understand EAPI is used to define a sort of super class
(in OO terms) for an ebuild.  (Feel free to correct).
I'm using Kito's prefixed ebuilds, which have the line
EAPI="prefix"
in them.

I'm not specifying the overlay right now, but I'm sure there are other
environment errors.  I'm assumming if I deal with them, this issue
will go away.

matt

-- 
gentoo-osx@gentoo.org mailing list



  reply	other threads:[~2005-12-16 19:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 23:21 [gentoo-osx] Attempt to use prefix on linux as secondary m h
2005-12-14 23:27 ` Nathan
2005-12-15  1:03   ` m h
2005-12-15  1:48     ` m h
2005-12-15  2:34       ` Kito
2005-12-15  6:17         ` m h
2005-12-15  6:35           ` Kito
2005-12-15  2:34 ` Kito
2005-12-15  7:31 ` Grobian
     [not found] ` <1134637115.30023.36.camel@sapc154>
2005-12-15 19:15   ` [gentoo-osx] " m h
2005-12-15 23:27     ` m h
2005-12-16  0:35       ` m h
2005-12-16  0:59         ` m h
2005-12-16  1:51           ` m h
2005-12-16 12:18             ` Brian Harring
2005-12-16 19:10               ` m h [this message]
2005-12-16 12:26           ` Brian Harring
2005-12-16 12:34             ` Brian Harring
2005-12-16  5:19         ` Nathan
2005-12-16 12:10           ` Grobian
2005-12-16 12:13         ` Grobian
2005-12-16 12:19           ` Grobian
2005-12-16 19:13             ` m h
2005-12-16 19:12           ` m h
2005-12-16 12:20         ` Brian Harring
2005-12-16 19:39           ` m h
2005-12-16 19:48             ` m h
2005-12-17 13:49 ` [gentoo-osx] " Grobian
2005-12-17 14:27   ` Grobian
2005-12-17 16:37     ` m h
2005-12-17 16:48   ` m h
2005-12-17 18:25     ` Grobian

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=e36b84ee0512161110hb2dc0d5ga3b334fe3fc27d77@mail.gmail.com \
    --to=sesquile@gmail.com \
    --cc=gentoo-osx@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