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] Mythtv problems
Date: Wed, 26 Oct 2011 23:44:14 +0100	[thread overview]
Message-ID: <20111026234414.1c34ab90@zaphod.digimed.co.uk> (raw)
In-Reply-To: <4EA868B4.1070005@gmail.com>

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

On Wed, 26 Oct 2011 15:08:20 -0500, Michael Sullivan wrote:

> > It's too late for this problem, but I'd recommend installing dmerge.
> > It takes a snapshot of what is installed after each emerge --sync,
> > and lets you roll back to a previous time (assuming the ebuilds are
> > still in the tree).

> Is it a problem that I share my /usr/portage directory from another
> machine through NFS?

I can't see that it will make a difference, except you'd need to run the
dmerge command manually, or via cron, instead of having portage run it
post-sync.


-- 
Neil Bothwick

"A computer is like an Old Testament god, with a lot of rules and no
mercy." -- Joseph Campbell

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

      parent reply	other threads:[~2011-10-26 22:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 14:23 [gentoo-user] Mythtv problems Michael Sullivan
2011-10-26 14:45 ` [gentoo-user] " Michael Sullivan
2011-10-26 18:20   ` Raffaele BELARDI
2011-10-26 16:07 ` [gentoo-user] " Neil Bothwick
2011-10-26 16:29   ` Michael Sullivan
2011-10-26 16:36     ` Mark Knecht
2011-10-26 18:31       ` Michael Sullivan
2011-10-26 19:03         ` Michael Sullivan
2011-10-26 19:05           ` Michael Sullivan
2011-10-26 19:45             ` Michael Sullivan
2011-10-26 19:51               ` Michael Sullivan
2011-10-26 20:01                 ` Michael Sullivan
2011-10-26 21:19               ` Michael Sullivan
2011-10-27 10:17                 ` Matt Harrison
2011-10-27  0:03         ` kashani
2011-10-27  0:15           ` Michael Sullivan
2011-10-26 18:46     ` Neil Bothwick
2011-10-26 20:08       ` Michael Sullivan
2011-10-26 21:25         ` Michael Sullivan
2011-10-26 21:46           ` Michael Schreckenbauer
2011-10-26 21:51             ` Michael Sullivan
2011-10-26 22:06               ` Michael Schreckenbauer
2011-10-26 22:14                 ` Michael Sullivan
2011-10-26 22:32                   ` Michael Schreckenbauer
2011-10-26 22:42                     ` Michael Sullivan
2011-10-26 22:53                       ` Michael Schreckenbauer
2011-10-26 22:59                         ` Michael Sullivan
2011-10-26 23:08                           ` Michael Schreckenbauer
2011-10-26 22:09               ` Michael Schreckenbauer
2011-10-26 22:30                 ` Michael Sullivan
2011-10-26 22:36                   ` Michael Schreckenbauer
2011-10-26 22:33                 ` Michael Sullivan
2011-10-26 22:58                   ` Michael Schreckenbauer
2011-10-26 23:10                     ` Michael Sullivan
2011-10-26 23:16                       ` Michael Schreckenbauer
2011-10-27  1:13                         ` [gentoo-user] Mythtv problems [SOLVED] Michael Sullivan
2011-10-27 10:08                           ` Michael Schreckenbauer
2011-10-26 22:44         ` Neil Bothwick [this message]

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=20111026234414.1c34ab90@zaphod.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