On Fri, Mar 27, 2020 at 5:17 AM Samuel Bernardo < samuelbernardo.m...@gmail.com> wrote:
> Hi again Michał, > On 3/27/20 11:48 AM, Michał Górny wrote: > > Nope, just ::gentoo. Minus ebuilds with RESTRICT=mirror. > > I have some doubts after reading the mirror documentation[1] in the > context of personal overlays (not official). > > There is two procedures defined as I could understand: > - manually upload a file to mirror://gentoo, scp it to > dev.gentoo.org:/space/distfiles-local > > - having SRC_URI defined as > SRC_URI="https://dev.gentoo.org/~myname/distfiles/${P}.tar.gz"; to avoid > namespace collisions with RESTRIC=mirror in ebuild would be uploaded > automatically > > The use of mirror://gentoo directly is a deprecated policy. So it must > be used https instead. > > 1) Did I understand it right? > > 2) What is dev.gentoo.org:~/public_html? Do this means that is only > available to Gentoo official developers the access to the mirror[2]? > > The Gentoo Mirror system is basically a set of scripts that syncs the ::gentoo repository, enumerates all URIs in SRC_URI for all ebuilds, and fetches them. It doesn't enumerate anything in any overlays. Overlay authors are required to point SRC_URI somewhere useful (typically to an upstream URI.) Gentoo Developers use "https://dev.gentoo.org/~user/distfiles"; as an origin URI for items where either Gentoo *is* the upstream, or there is no upstream (e.g. a custom Gentoo patchset.) Any origin URI can be used; this just happens to be some free hosting that Gentoo Developers have access to use. -A > Best, > > Samuel > > [1] https://devmanual.gentoo.org/general-concepts/mirrors/index.html > > [2] https://wiki.gentoo.org/wiki/Project:Infrastructure/Developer_Webspace > > >
