public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Switch from PORTDIR and PORTDIR_OVERLAY to repos.conf - WAS: Moving the portage tree to /var
Date: Thu, 30 Oct 2014 07:17:10 -0400	[thread overview]
Message-ID: <54521E36.4080907@libertytrek.org> (raw)
In-Reply-To: <m2qjgu$at0$1@ger.gmane.org>

On 10/29/2014 7:37 AM, Martin Vaeth <martin@mvath.de> wrote:
> The long-term plans are to drop PORTDIR and PORTDIR_OVERLAY
> completely, the reason being that it is not flexible enough:
> With repos.conf you can specify details for every repository,
> you are not even forced to have a *single* major repository
> (AFAIK, this is called mix-ins in some other package managers),
> etc.

Ok, thanks Martin/guys...

So, the short answer is:

"Don't worry about it, if/when something needs to be done to prevent
breakage, we will let you know ahead of time via a news item or other
appropriate method."

Which sounds like the right thing to do for those of us who prefer
stability to (too much) bleeding edge?

But - for those of us who, while preferring stability, also might like
to get a jump on things *if* switching to repos.conf now is:

 a) easy,
 b) fully supported, and
 c) considered perfectly stable,

would it be possible for someone with intimate knowledge of the details
to write up a wiki page for how to go about it?

Thanks again!


  reply	other threads:[~2014-10-30 11:18 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                         ` Tanstaafl [this message]
2014-10-08 11:36           ` [gentoo-user] " Tanstaafl
2014-10-07 15:37 ` Neil Bothwick
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=54521E36.4080907@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --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