public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dev-portage <dev-portage@gentoo.org>
Subject: Re: [gentoo-dev] Re: [RFC] Removing obsolete thick Manifest compatibility from MetaManifests
Date: Tue, 05 Nov 2019 14:17:09 +0100	[thread overview]
Message-ID: <04f0743fee71bbd6a072eadcd7f510c5fe1c48b4.camel@gentoo.org> (raw)
In-Reply-To: <5be90d9e-d746-2dc5-ed82-cde78c985949@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

On Tue, 2019-11-05 at 14:01 +0100, Michael Haubenwallner wrote:
> Hi,
> 
> On 10/24/19 2:37 PM, Michał Górny wrote:
> > Hello,
> > 
> > TL;DR: I'd like to disable thick Manifest support in Portage, in order
> > to disable some of the compatibility quirks from MetaManifest format. 
> > All files would still be verified by gemato.
> > WDYT?
> > 
> 
> I'm using Gentoo Prefix as a Meta Distribution, where I can not use the
> Gentoo infrastructure, but have to provide the master services on my own.
> 
> While I've been able to set up rsync & distfiles master ~10 years ago,
> where I haven't discovered any docs for so far, I feel lost when I think
> of setting up additional master services for gemato without some docs.
> 
> Facing the removal of thick Manifest support (which I don't want to block
> in any way), I've started to search for some docs how to set up these
> additional master services to support gemato, but failed.
> 
> What I've found is the Infrastructure wiki project, providing a list of
> servers maintained by infra, but nothing about how to set them up.
> 
> Did I miss something?
> 

gemato has commands to create and update MetaManifests.  Also there's
(much faster) trivial script in utils/ directory of gemato.

The relevant infra script is:
https://gitweb.gentoo.org/infra/mastermirror-scripts.git/tree/rsync-gen.sh#n243

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

      reply	other threads:[~2019-11-05 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 12:37 [gentoo-dev] [RFC] Removing obsolete thick Manifest compatibility from MetaManifests Michał Górny
2019-11-05 13:01 ` [gentoo-dev] " Michael Haubenwallner
2019-11-05 13:17   ` Michał Górny [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=04f0743fee71bbd6a072eadcd7f510c5fe1c48b4.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=dev-portage@gentoo.org \
    --cc=gentoo-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