From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [EAPI 8 RFC] Selective fetch/mirror (un-)restriction
Date: Mon, 16 Dec 2019 13:39:02 +0100 [thread overview]
Message-ID: <293656848f42786552da59ad307058d597efa026.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
Hello, everyone.
I'd like to start a series of mails dedicated to features proposed for
including in EAPI 8. For a start, I'd like to discuss the topic of
selective fetch restriction [1]. It has been discussed at least in 2013
[2], and since it's finally got chance to be included, I think it's
worthwhile to rehash it.
The problem
===========
Fetch/mirror restriction as of now can only be applied to all distfiles
at once. This causes problems in the (rather rare) case when we'd like
to add some additional files to SRC_URI that do not require the big
restriction. As a result, the user is forced to manually fetch all
the files even if only one truly requires it.
Proposed solution
=================
The current proposal is based on extending the current URI syntax to
permit excluding individual files from the restriction. The idea is to
prepend 'fetch+' to protocol to undo fetch restriction, or to prepend
'mirror+' to undo fetch & mirror restrictions.
Example 1: removing mirror restriction from files
RESTRICT="mirror"
SRC_URI="https://example.com/you-cant-mirror-this.tar.bz2
mirror+https://example.com/but-you-can-mirror-this.tar.gz"
Example 2: removing fetch & mirror restriction from files
RESTRICT="fetch"
SRC_URI="https://example.com/you-cant-fetch-this.zip
mirror+https://example.com/but-you-can-mirror-this.tar.gz"
Example 3: removing fetch restriction while leaving mirror restriction
RESTRICT="fetch"
SRC_URI="https://example.com/you-cant-fetch-this.zip
fetch+https://example.com/you-cant-mirror-this.tar.bz2"
Comments
========
WDYT?
References
==========
[1] https://bugs.gentoo.org/371413
[2] https://archives.gentoo.org/gentoo-dev/message/b0823618d5d3cc61bbed1e88dc2f144d
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2019-12-16 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 12:39 Michał Górny [this message]
2019-12-16 13:09 ` [gentoo-dev] [EAPI 8 RFC] Selective fetch/mirror (un-)restriction Francesco Riosa
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=293656848f42786552da59ad307058d597efa026.camel@gentoo.org \
--to=mgorny@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