public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Old news items
Date: Wed, 16 Dec 2015 09:04:46 -0800	[thread overview]
Message-ID: <567199AE.108@gentoo.org> (raw)
In-Reply-To: <n4s3b0$1uj$1@ger.gmane.org>

On 12/16/2015 08:26 AM, Michael Palimaka wrote:
> On a fresh amd64 stage3 a user is presented with fourteen news items to
> read, and three[1][2][3] of these are directly related to Portage.
> 
> In order to improve the out-of-box experience, please review them for
> relevance and consider removing or restricting any that are not.
> 
> 1:
> https://gitweb.gentoo.org/data/gentoo-news.git/tree/2012-05-21-portage-config-protect-if-modified/2012-05-21-portage-config-protect-if-modified.en.txt
> 2:
> https://gitweb.gentoo.org/data/gentoo-news.git/tree/2013-06-07-portage-preserve-libs-default/2013-06-07-portage-preserve-libs-default.en.txt

Thanks, I've dropped the above 2 items.

> 3:
> https://gitweb.gentoo.org/data/gentoo-news.git/tree/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt

This one is probably still somewhat relevant. However, we should
probably deprecate PORTDIR and PORTDIR_OVERLAY (with loud warnings from
portage when they are set), and possibly send out another news item for
that.
-- 
Thanks,
Zac


      reply	other threads:[~2015-12-16 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 16:26 [gentoo-portage-dev] Old news items Michael Palimaka
2015-12-16 17:04 ` Zac Medico [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=567199AE.108@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@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