public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Introduce Manual manipulation during an emerge
Date: Fri, 12 Jun 2009 21:16:04 +0100	[thread overview]
Message-ID: <A023B8C7-0009-45AC-B974-668D51F53F91@stellar.eclipse.co.uk> (raw)
In-Reply-To: <uprd9cjeu.fsf@newsguy.com>


On 12 Jun 2009, at 20:59, Harry Putnam wrote:
> ...
> For something like this it seems way overkill to have a separate
> custom /usr/local/portage where I build my own.  Especially since I
> find that whole process difficult and way overkill for this problem.
>
> Further its something that will almost certainly be fixed soon and
> won't be something I have to attend to again.

If you think that's the case then just mask the current version of  
procmail in /etc/portage/package.mask & remerge procmail. An older  
version without this bug will be installed & when an updated version  
is available portage will install it automagically.

I consider /usr/local/portage to be essential, because there's most  
always a package or three on my systems which I can't get through the  
regular tree, or which i wish to version bump myself. I don't consider  
this a hassle because I could create the updated ebuild with patch in  
a few minutes.

Because I most always check some reference resources when I do this, I  
can't quickly explain to you how to maintain this tree yourself. I  
think the time it would take you to learn this would be well-spent, as  
I'm sure you'll eventually need to use a /usr/local/portage package  
again in the future. Like I say, once you know how, it becomes easy.  
But if you consider it a hassle, just mask the buggy version of  
procmail & forget about the problem.

Stroller. 



  reply	other threads:[~2009-06-12 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 19:59 [gentoo-user] Introduce Manual manipulation during an emerge Harry Putnam
2009-06-12 20:16 ` Stroller [this message]
2009-06-12 20:57   ` [gentoo-user] " Harry Putnam
2009-06-12 20:43 ` [gentoo-user] " Mike Kazantsev
2009-06-12 20:58   ` [gentoo-user] " Harry Putnam
2009-06-12 21:22   ` Harry Putnam
2009-06-12 23:20     ` Arttu V.
2009-06-12 23:39       ` Harry Putnam
2009-06-13  0:19         ` Arttu V.
2009-06-13 13:57           ` Harry Putnam

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=A023B8C7-0009-45AC-B974-668D51F53F91@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.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