From: Francesco Riosa <vivo75@gmail.com>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [EAPI 8 RFC] Selective fetch/mirror (un-)restriction
Date: Mon, 16 Dec 2019 14:09:50 +0100 [thread overview]
Message-ID: <CAD6zcDyz2FbYB0++G_sV00qgeDeLcuUBZ9umFHGMakDn4a4f=g@mail.gmail.com> (raw)
In-Reply-To: <293656848f42786552da59ad307058d597efa026.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
Il giorno lun 16 dic 2019 alle ore 13:39 Michał Górny <mgorny@gentoo.org>
ha scritto:
>
>
> Comments
> ========
> WDYT?
>
> what about getting rid of RESTRICT="fetch" and manage everything inside
SRC_URI? Would that be technically feasible?
Ideally marking only the not re-distributable download and leaving
untouched the others
[-- Attachment #2: Type: text/html, Size: 676 bytes --]
next prev parent reply other threads:[~2019-12-16 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 12:39 [gentoo-dev] [EAPI 8 RFC] Selective fetch/mirror (un-)restriction Michał Górny
2019-12-16 13:09 ` Francesco Riosa [this message]
2019-12-16 13:33 ` Ulrich Mueller
2019-12-16 15:24 ` Rich Freeman
2019-12-16 13:16 ` Ulrich Mueller
2019-12-17 15:21 ` Michał Górny
2019-12-20 9:20 ` Michał Górny
2019-12-20 13:35 ` Ulrich Mueller
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='CAD6zcDyz2FbYB0++G_sV00qgeDeLcuUBZ9umFHGMakDn4a4f=g@mail.gmail.com' \
--to=vivo75@gmail.com \
--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