public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Moving the portage tree to /var
Date: Tue, 7 Oct 2014 16:37:47 +0100	[thread overview]
Message-ID: <20141007163747.591b894f@hactar.digimed.co.uk> (raw)
In-Reply-To: <4473472.7D6UrCk1jI@wstn>

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

On Tue, 07 Oct 2014 16:09:54 +0100, Peter Humphrey wrote:

> This seems to work OK, except for eix-update, which gives me this:
> 
> $ eix-update
> Reading Portage settings ..
> Building database (/var/cache/eix/portage.eix) ..
> [0] "gentoo" /var/portage/ (cache: metadata-md5-or-flat)
>      Reading category 162|162 (100%) Finished             
> [1] "" /usr/portage (cache:
> parse|ebuild*#metadata-md5#metadata-flat#assign) Reading category
> parse|162|162 (100%) EMPTY!
> [...]
> 
> Evidently something is still pointing to /usr/portage, but I can't see
> what.

I've just installed a new system with the tree in /var from the outset
and no /usr/portage at all, and eix behaves like this (I hadn't noticed
until you pointed it out) so it may be the /usr/portage path is hard
coded.

This doesn't cause any problems but now you have pointed it out it is
going to annoy me.


-- 
Neil Bothwick

A clean desk is a sign of a cluttered desk drawer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2014-10-07 15:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 15:09 [gentoo-user] Moving the portage tree to /var Peter Humphrey
2014-10-07 15:29 ` Bruce Schultz
2014-10-07 15:39   ` Peter Humphrey
2014-10-07 16:08     ` Neil Bothwick
2014-10-07 21:48       ` Mick
2014-10-07 21:56         ` Mike Gilbert
2014-10-07 22:03           ` Mick
2014-10-25 13:57             ` Tanstaafl
2014-10-25 16:45               ` Michael Orlitzky
2014-10-25 17:49                 ` Mick
2014-10-25 17:59                   ` Michael Orlitzky
2014-10-26 14:02                     ` [gentoo-user] " Martin Vaeth
2014-10-26 14:46                       ` Michael Orlitzky
2014-10-26  8:56                 ` [gentoo-user] " Peter Humphrey
2014-10-27 15:45                 ` Tanstaafl
2014-10-27 19:06                   ` Alan McKinnon
2014-10-27 20:05                     ` Mike Gilbert
2014-10-29 11:37                       ` [gentoo-user] " Martin Vaeth
2014-10-30 11:17                         ` [gentoo-user] Switch from PORTDIR and PORTDIR_OVERLAY to repos.conf - WAS: " Tanstaafl
2014-10-08 11:36           ` [gentoo-user] " Tanstaafl
2014-10-07 15:37 ` Neil Bothwick [this message]
2014-10-07 15:57 ` Tomas Mozes
2014-10-07 16:02   ` Tomas Mozes

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=20141007163747.591b894f@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@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