| 1 |
Hi Alec, |
| 2 |
|
| 3 |
On 3/27/20 7:27 PM, Alec Warner wrote: |
| 4 |
> The Gentoo Mirror system is basically a set of scripts that syncs the |
| 5 |
> ::gentoo repository, enumerates all URIs in SRC_URI for all ebuilds, |
| 6 |
> and fetches them. |
| 7 |
> It doesn't enumerate anything in any overlays. Overlay authors are |
| 8 |
> required to point SRC_URI somewhere useful (typically to an upstream URI.) |
| 9 |
> |
| 10 |
> Gentoo Developers use "https://dev.gentoo.org/~user/distfiles" as an |
| 11 |
> origin URI for items where either Gentoo *is* the upstream, or there |
| 12 |
> is no upstream (e.g. a custom Gentoo patchset.) Any origin URI can be |
| 13 |
> used; this just happens to be some free hosting that Gentoo Developers |
| 14 |
> have access to use. |
| 15 |
> |
| 16 |
> -A |
| 17 |
|
| 18 |
Thank you for your clarification. |
| 19 |
|
| 20 |
So what happens when RESTRIC=mirror is used inside ebuild for an overlay |
| 21 |
in git.gentoo.org? |
| 22 |
|
| 23 |
So, thinking on site reliability, should it be a good choice to upload |
| 24 |
the necessary tar.gz, for example, to gitlab or github community |
| 25 |
services using git lfs as an alternative to "https://dev.gentoo.org/"? |
| 26 |
|
| 27 |
Best, |
| 28 |
|
| 29 |
Samuel |
Archives