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,
	Michael Haubenwallner <michael.haubenwallner@salomon.at>
Subject: Re: [gentoo-osx] PREFIX the next generation...
Date: Mon, 19 Dec 2005 17:33:23 -0800	[thread overview]
Message-ID: <e36b84ee0512191733r1b693da5i8d1924bd6694f12@mail.gmail.com> (raw)
In-Reply-To: <3BA733F8-3628-4896-8501-B7D7FCFDE58E@gentoo.org>

More progress...
So after tweaking the portage overlay tree and adding some symlinks,
portage will calculate the deps for emerge -av system.  But when I try
to emerge the 53 packages it fails because it is trying to merge to
"/".... ie:
Do you want me to merge these packages? [Yes/No] y
>>> emerge (1 of 53) sys-devel/patch-2.5.9-r1 to /
!!! File system problem. (Bad Symlink?)
!!! Fetching may fail: [Errno 2] No such file or directory: ''
!!! No write access to /
!!! File patch-2.5.9.tar.gz isn't fetched but unable to get it.

----------------
Note the "/" in the first line.  Still my environment is missing
something.  But I'm getting closer....

On 12/19/05, Kito <kito@gentoo.org> wrote:
>
> On Dec 19, 2005, at 4:49 PM, m h wrote:
>
> > Also why is emerge -av system trying to installing portage2.1?
> >
>
> Because portage is part of the base system packages. You manually
> installed portage(i.e. not via an ebuild) so portage itself doesn't
> know it is installed(hope that made sense). In other words, you have
> an empty world file, and portage is trying to satisfy all the deps
> specified in your base profile.
>
> Take a look at PORTDIR/profiles/base/packages
>
> On a side note, I put a placeholder on a wiki page[1] so we can start
> trying to consolidate all of our various notes/efforts. Alas, I
> didn't have time today to put anything useful...
>
> --Kito
>
> [1] http://gentoo-wiki.com/Portage-prefix
> --
> gentoo-osx@gentoo.org mailing list
>
>

-- 
gentoo-osx@gentoo.org mailing list



  reply	other threads:[~2005-12-20  1:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 21:07 [gentoo-osx] PREFIX the next generation m h
2005-12-19 21:21 ` [gentoo-osx] " m h
2005-12-19 21:26   ` m h
2005-12-19 21:30     ` Grobian
2005-12-19 21:25 ` [gentoo-osx] " Grobian
2005-12-19 22:49   ` m h
2005-12-19 23:20     ` Kito
2005-12-20  1:33       ` m h [this message]
2005-12-20  6:32         ` Grobian
2005-12-20  9:23           ` Grobian
2005-12-20 20:11             ` m h
2005-12-20 20:53               ` Grobian
2005-12-20 23:00                 ` m h
2005-12-20 23:20                   ` m h
2005-12-21  0:09                     ` m h
2005-12-21 12:50                       ` Grobian
2005-12-22  6:57                         ` Brian Harring
2005-12-22  7:02                           ` Brian Harring
2005-12-22 10:35                             ` Grobian
2005-12-21 13:26                       ` Grobian
2005-12-20 22:18               ` Kito
2005-12-20 22:22                 ` Kito
2005-12-21  9:39     ` Michael Haubenwallner

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=e36b84ee0512191733r1b693da5i8d1924bd6694f12@mail.gmail.com \
    --to=sesquile@gmail.com \
    --cc=gentoo-osx@lists.gentoo.org \
    --cc=michael.haubenwallner@salomon.at \
    /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