public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] re: resolving blocked packages [media-video/ffmpeg-1.2:0]
Date: Mon, 4 Nov 2013 18:41:08 -0600	[thread overview]
Message-ID: <20131105004108.GI22282@server> (raw)
In-Reply-To: <201311042243.08617.michaelkintzios@gmail.com>

On Mon, Nov 04, 2013 at 10:43:07PM +0000, Mick wrote:
> On Monday 04 Nov 2013 19:51:32 Alexander Kapshuk wrote:
> > On 11/03/2013 02:27 AM, Daniel Campbell wrote:
> > > For starters, you should probably merge package.keywords into
> > > package.accept_keywords; the latter is the "new" standard name, though
> > > Portage will likely support the old names for a while. Just a heads-up
> > > on that.
> > 
> > Thanks for a heads-up. I did as you suggested.
> 
> Is there going to be a portage news article on this, or did I miss it?

It wasn't two or three years ago...

mingdao@server ~ $ eselect news read 5
2012-09-09-make.conf-and-make.profile-move
  Title                     make.conf and make.profile move
  Author                    Jorge Manuel B. S. Vicetto <jmbsvicetto@gentoo.org>
  Posted                    2012-09-09
  Revision                  1

Starting next week, new stages will have make.conf and make.profile
moved from /etc to /etc/portage. This is a change in the installation
defaults, that will only affect new installs so it doesn't affect
current systems.

Current users don't need to do anything. But if you want to follow the
preferred location, you may want to take the chance to move the files
in your system(s) to the new location.
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting


  parent reply	other threads:[~2013-11-05  0:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 17:08 [gentoo-user] re: resolving blocked packages [media-video/ffmpeg-1.2:0] Alexander Kapshuk
2013-11-02 10:49 ` Daniel Campbell
2013-11-02 11:07   ` Alan McKinnon
2013-11-02 15:29     ` Daniel Campbell
2013-11-02 19:06       ` Alexander Kapshuk
2013-11-03  0:27         ` Daniel Campbell
2013-11-03  5:40           ` Alexander Kapshuk
2013-11-03  9:42             ` Peter Humphrey
2013-11-04 19:56               ` Alexander Kapshuk
2013-11-04 19:51           ` Alexander Kapshuk
2013-11-04 22:43             ` Mick
2013-11-04 23:36               ` Alan McKinnon
2013-11-05  0:15                 ` Dale
2013-11-05  0:41               ` Bruce Hill [this message]
2013-11-05  6:15                 ` [gentoo-user] " Nuno J. Silva (aka njsg)
2013-11-05  8:05                   ` Mick
2013-11-05 14:40                   ` Bruce Hill
2013-11-09  8:13                     ` Mick
2013-11-03  8:26         ` [gentoo-user] " Alan McKinnon
2013-11-04 20:03           ` [gentoo-user] re: resolving blocked packages [media-video/ffmpeg-1.2:0] [SOLVED] Alexander Kapshuk

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=20131105004108.GI22282@server \
    --to=daddy@happypenguincomputers.com \
    --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