public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-releng@lists.gentoo.org,
	"M. J. Everitt" <m.j.everitt@iee.org>,
	gentoo-dev@lists.gentoo.org
Subject: [gentoo-releng] Re: [gentoo-dev] rfc: moving default location of portage tree
Date: Mon, 9 Jul 2018 15:54:35 -0700	[thread overview]
Message-ID: <50aa6222-d97c-6fd0-0884-23b27f494135@gentoo.org> (raw)
In-Reply-To: <8b47a97d-37be-652a-0298-7e7082506b53@iee.org>


[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]

On 07/09/2018 03:27 PM, M. J. Everitt wrote:
> On 09/07/18 23:12, Zac Medico wrote:
>> On 07/09/2018 02:34 PM, Kristian Fiskerstrand wrote:
>>> I'd mostly argue any such change should only affect new systems
>>>
>> Yes, changing defaults for existing systems would be annoying.
>>
>> My recommendation is to have catalyst set the new defaults in the stage
>> tarballs.
>>
>> When sys-apps/portage changes its internal defaults, I'd like for the
>> upgrade process to call a tool that generates configuration files when
>> necessary to ensure that the existing paths remain constant.
> I think it should be possible for RelEng to make a start on catalyst
> updates - is there anything that would inhibit going ahead with this,
> potentially?

No, nothing. Whatever catalyst puts it the default config will become
our new default.
-- 
Thanks,
Zac


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2018-07-09 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180709172136.GA17068@linux1.home>
     [not found] ` <1531161811.1159.13.camel@gentoo.org>
     [not found]   ` <20180709201113.GB17593@linux1.home>
     [not found]     ` <1531167218.1159.15.camel@gentoo.org>
     [not found]       ` <CAGfcS_ke5Esm_3JS_1bzSLv=ZjabdmBnv_tA-nJkt4+rKqGTww@mail.gmail.com>
     [not found]         ` <20180709211410.GA17986@linux1.home>
     [not found]           ` <2f7c8b18-8c5d-2931-14a7-9d6d1e00526d@gentoo.org>
     [not found]             ` <29b55e16-bb2e-5a98-13e2-e1482441b417@gentoo.org>
2018-07-09 22:27               ` [gentoo-releng] Re: [gentoo-dev] rfc: moving default location of portage tree M. J. Everitt
2018-07-09 22:54                 ` Zac Medico [this message]
     [not found]                   ` <20180710200923.GA21918@linux1.home>
2018-07-10 21:35                     ` M. J. Everitt

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=50aa6222-d97c-6fd0-0884-23b27f494135@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-releng@lists.gentoo.org \
    --cc=m.j.everitt@iee.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