From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage Feature Request: making thirdpartymirrors easier to manage
Date: Sun, 12 Jan 2014 08:16:01 +1300 [thread overview]
Message-ID: <CAATnKFCg4Pf_ca7YhQWikuXa-aqSq9JmAgQrHAQmLUKCpAcfLQ@mail.gmail.com> (raw)
In-Reply-To: <20140110055849.50796563@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On 10 January 2014 17:58, Michał Górny <mgorny@gentoo.org> wrote:
>
> Just to be clear, what is the exact use case for this? I can't think
> of a really good reason to manipulate mirror lists in subsequent repos.
>
For Perl, in ::gentoo , its considered not too optimal to have backpan
listed as a mirror, and its unnesscary, as ::gentoo gets to mirror
everything on cpan anyway, so that there's no problem when upstream delete
the version gentoo is using from cpan.
But in the overlay, we don't have the luxury of a mirror, so we have
backpan listed as a mirror for when cpan deletes a release.
diff <( grep cpan
/var/paludis/repositories/perl-git/profiles/thirdpartymirrors ) <( grep
cpan /usr/portage/profiles/thirdpartymirrors )
1c1
< cpan http://search.cpan.org/CPAN http://cpan.hexten.net/
http://cpan.cpantesters.org http://www.cpan.org http://backpan.perl.org
---
> cpan http://search.cpan.org/CPAN http://www.cpan.org
So here, it would be nicer if we could simply specify new mirrors instead
of having to override the whole thing.
--
Kent
[-- Attachment #2: Type: text/html, Size: 2014 bytes --]
next prev parent reply other threads:[~2014-01-11 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:20 [gentoo-dev] Portage Feature Request: making thirdpartymirrors easier to manage Robin H. Johnson
2014-01-06 21:09 ` Alex Xu
2014-01-07 21:12 ` Robin H. Johnson
2014-01-08 15:11 ` Jeroen Roovers
2014-01-08 18:37 ` Alex Xu
2014-01-09 2:14 ` Jeroen Roovers
2014-01-09 2:23 ` Alec Warner
2014-01-09 15:14 ` Ben Kohler
2014-01-09 7:59 ` "Paweł Hajdan, Jr."
2014-01-09 15:26 ` Ben Kohler
2014-01-10 4:58 ` Michał Górny
2014-01-10 6:05 ` Alec Warner
2014-01-11 18:27 ` Gordon Pettey
2014-01-11 19:16 ` Kent Fredric [this message]
2014-01-11 19:19 ` Kent Fredric
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=CAATnKFCg4Pf_ca7YhQWikuXa-aqSq9JmAgQrHAQmLUKCpAcfLQ@mail.gmail.com \
--to=kentfredric@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=robbat2@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