| 1 |
Diego Elio Pettenò schrieb: |
| 2 |
> Hello everybody, |
| 3 |
> |
| 4 |
> I have already said this before, but it looks like nobody cared. We have |
| 5 |
> a problem for what concerns Gentoo-generated distfiles. |
| 6 |
> |
| 7 |
> This includes custom snapshots, custom packages, patches, patchsets, and |
| 8 |
> so on so forth. While it was infra that (back when I joined at least) |
| 9 |
> asked not to use dev.gentoo.org for hosting said fails and rather prefer |
| 10 |
> to use mirror://gentoo/, they already stated that it's not a problem to |
| 11 |
> do so until we have a proper system in place (system that has been |
| 12 |
> considered and worked on for quite a bit already and yet is not |
| 13 |
> available). |
| 14 |
> |
| 15 |
> Unfortunately, as long as the mirror://gentoo/ option is still |
| 16 |
> maintained, we'll end up with situations like today's gnuconfig that |
| 17 |
> couldn't be fetched, causing all ~arch users to see the same failure, |
| 18 |
> because the distfile wasn't uploaded to the staging area. Of course the |
| 19 |
> same could happen with a stable SRC_URI, but then it would fail after |
| 20 |
> hitting that, rather than going through half the gentoo mirrors trying |
| 21 |
> to find a file that is not there. |
| 22 |
> |
| 23 |
> So, anybody has reasons beside laziness, or concern for infra's disk |
| 24 |
> usage (that argument is allowed to come only from infra members!), to |
| 25 |
> not go this route? |
| 26 |
> |
| 27 |
|
| 28 |
I see no improvement from this proposal. If a tarball is not uploaded, the users will always fail to |
| 29 |
get it, independent from the place, where it should be going to. And even if you put the |
| 30 |
dev.gentoo.org address in SRC_URI, portage will first check the mirrors before it checks SRC_URI, so |
| 31 |
this would in the end result in even 1 more download try without success. |
| 32 |
|
| 33 |
The argument about dropped tarballs, once the ebuilds gets removed might weight a bit more, but you |
| 34 |
cannot depend on other upstream keeping their tarballs around forever, so i see no requirement for |
| 35 |
us preserving only specific tarballs (those created by our devs), while upstream tarballs could |
| 36 |
already be gone and are not preserved, once the ebuild for it is gone. |
Archives