public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Felix Bier <Felix.Bier@rohde-schwarz.com>
To: "gentoo-catalyst@lists.gentoo.org" <gentoo-catalyst@lists.gentoo.org>
Subject: Re:  [Newsletter] Re: [gentoo-catalyst] Re: [PATCH] Documentation: Make existing multi-overlay support more explicit
Date: Tue, 10 Nov 2020 00:51:05 +0000	[thread overview]
Message-ID: <b9f95ef38d4399adb53e8b81dd67a5250a79733f.camel@rohde-schwarz.com> (raw)
In-Reply-To: <CAEdQ38GpfNk-K6OG148G+xsZnVaMXYnLHYutmkEXD0n8+LOa0A@mail.gmail.com>

Am Freitag, den 30.10.2020, 11:54 -0400 schrieb Matt Turner:
> Looks good, though I wonder if we shouldn't rename 'portage_overlay'
> as well? 'repos' or something?
> 
> I'm going to change the custom .spec format over to TOML soon, so I
> can do that then unless you want to handle it.

I agree that 'portage_overlay' should be renamed. It seems 'repos' is
already taken (for the portage snapshot feature). We could rename
'repos' -> 'repos_storedir' and then 'portage_overlay' -> 'repos', but
I would prefer to keep this step separate from the PORTDIR_OVERLAY
removal.

My plan for the next steps would be:

 * Remove PORTDIR as well
 * Remove copying of overlays in favor of mounting
 * Somehow merge 'snapshot_treeish' and 'portage_overlay' into a single
option (called e.g. 'repos'), which takes a list of repo snapshots. So
there would no longer be a special main repo.

> 
> I'll commit this if you will give me your Signed-off-by for the
> patches. Thanks!


  reply	other threads:[~2020-11-10  0:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 18:45 [gentoo-catalyst] [PATCH] Documentation: Make existing multi-overlay support more explicit Felix Bier
2020-10-18 15:07 ` [gentoo-catalyst] " Felix Bier
2020-10-30 15:54   ` Matt Turner
2020-11-10  0:51     ` Felix Bier [this message]
2020-11-10  0:56     ` [Newsletter] " Felix Bier

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=b9f95ef38d4399adb53e8b81dd67a5250a79733f.camel@rohde-schwarz.com \
    --to=felix.bier@rohde-schwarz.com \
    --cc=gentoo-catalyst@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