public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New distfile mirror layout
Date: Wed, 23 Oct 2019 01:16:51 -0400	[thread overview]
Message-ID: <79d2c3f3-9c9a-4247-205a-b929ee0a582c@gentoo.org> (raw)
In-Reply-To: <20191021231324.7c9d05d9@katipo2.lan>

On 10/21/2019 06:13, Kent Fredric wrote:
> On Sun, 20 Oct 2019 16:57:54 -0400
> Joshua Kinard <kumba@gentoo.org> wrote:
> 
>> I know we've got a ton of Perl packages for the core set of Perl modules,
>> but doesn't the CPAN eclass also have the capability to auto-generate an
>> ebuild package for virtually any Perl package distributed via CPAN?  Can
>> that logic be used with the CTAN system in its own eclass and then we remove
>> the 16k+ texlive modules off of our mirrors completely?  Or at the worst, we
>> might just have to generate ebuilds for texlive modules and treat them as
>> discrete, installed packages.
> 
> - Perl packages never have more than 1:1 source archives per ebuild
> - Perl upstream naming doesn't habitually use "perl-" as an archive prefix
> - Everything that is packaged for Perl in Gentoo is mirrored to the
>   Gentoo distfiles mirror, and this causes no issues.
> 
> So I don't think any comparison here makes sense.

I have to disagree on the "doesn't make sense" bit.  Regardless of what it
is that TexLive is packaging, the problem that I feel exists is storing
these macro packages on our mirrors is what is responsible for 20% of *all*
distfiles that we store.  That's lopsided that a small collection of
ebuilds, due to the way their build logic is architected, has that many
distfiles on the mirrors.

It's scenarios like that which led to Michał developing the GLEP the way he
did.  His approach is more broad, seeking to future-proof the mirroring
issue regardless of package mirroring decisions, whereas I'm more curious
why texlive needs all of those packages on our mirrors when it appears to
have a fairly comprehensive mirroring system of its own.  Why reinvent the
wheel?

Since CTAN exists as a worldwide mirroring system, I think at a minimum, we
should try to fetch from that directly instead of mirroring them on our own
systems and partner mirrors.  Or we could go the other way and become an
official CTAN mirror ourselves.  After all, if we're going to reinvent the
wheel, do all four instead of just one.

And for Perl or Python, I think we should be making an effort to leverage
their respective mirroring systems first before putting their distfiles onto
our mirrors.  Perl's got CPAN, and Python has pypi.  For things that don't
exist on those systems, then we use our mirrors.

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
rsa6144/5C63F4E3F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943

"The past tempts us, the present confuses us, the future frightens us.  And
our lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic


  reply	other threads:[~2019-10-23  5:17 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 13:41 [gentoo-dev] New distfile mirror layout Michał Górny
2019-10-18 19:53 ` Richard Yao
2019-10-18 20:49   ` Michał Górny
2019-10-19  1:09     ` Richard Yao
2019-10-19  6:17       ` Michał Górny
2019-10-19  8:20         ` Richard Yao
2019-10-19 19:26       ` Richard Yao
2019-10-19 20:02         ` Michał Górny
2019-10-19 22:48           ` Richard Yao
2019-10-22  0:46   ` James Cloos
2019-10-19 13:31 ` Fabian Groffen
2019-10-19 13:53   ` Michał Górny
2019-10-19 23:24 ` Joshua Kinard
2019-10-19 23:57   ` Alec Warner
2019-10-20  0:14     ` Joshua Kinard
2019-10-20  6:51   ` Michał Górny
2019-10-20  8:25     ` Joshua Kinard
2019-10-20  8:32       ` Michał Górny
2019-10-20  9:21         ` Joshua Kinard
2019-10-20  9:44           ` Michał Górny
2019-10-20 20:57             ` Joshua Kinard
2019-10-21  0:05               ` Joshua Kinard
2019-10-21  5:51                 ` Ulrich Mueller
2019-10-21 10:17                 ` Kent Fredric
2019-10-21 21:34                 ` Mikle Kolyada
2019-10-21 10:13               ` Kent Fredric
2019-10-23  5:16                 ` Joshua Kinard [this message]
2019-10-29 16:35                   ` Kent Fredric
2019-10-20 17:09       ` Matt Turner
2019-10-21 16:42     ` Richard Yao
2019-10-21 23:36       ` Matt Turner
2019-10-23  5:18         ` Joshua Kinard
2019-10-23 17:06           ` William Hubbs
2019-10-23 18:38             ` William Hubbs
2019-10-23 22:04           ` William Hubbs
2019-10-24  4:30             ` Michał Górny
2019-10-22  6:51       ` Jaco Kroon
2019-10-22  8:43         ` Ulrich Mueller
2019-10-22  8:46           ` Jaco Kroon
2019-10-23 23:47         ` ext4 readdir performance - was " Richard Yao
2019-10-24  0:01           ` Richard Yao
2019-10-23  1:21       ` Rich Freeman
2019-10-28 23:24     ` Chí-Thanh Christopher Nguyễn
2019-10-29  4:27       ` Michał Górny
2019-10-29  9:34         ` Fabian Groffen
2019-10-29 11:11           ` Michał Górny
2019-10-29 12:23             ` Ulrich Mueller
2019-10-29 12:43               ` Michał Górny
2019-10-29 13:03                 ` Ulrich Mueller
2019-10-29 13:09                   ` Ulrich Mueller
2019-10-29 13:52                     ` Michał Górny
2019-10-29 14:17                       ` Ulrich Mueller
2019-10-29 14:33                         ` Fabian Groffen
2019-10-29 14:45                           ` Michał Górny
2019-10-29 14:56                             ` Fabian Groffen
2019-10-29 13:51                   ` Michał Górny

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=79d2c3f3-9c9a-4247-205a-b929ee0a582c@gentoo.org \
    --to=kumba@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