From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Eselect repository feature request
Date: Tue, 20 Jun 2023 13:26:21 -0400 [thread overview]
Message-ID: <CAJ0EP43LeSReqT641=+TcEE=nmF2ktG3_zNoCd+zjxY65BRL7A@mail.gmail.com> (raw)
In-Reply-To: <703cdee8-b322-6c49-be13-efd10426ea6b@gentoo.org>
On Tue, Jun 20, 2023 at 1:08 PM Florian Schmaus <flow@gentoo.org> wrote:
>
> On 20.06.23 16:41, TOMAS FABRIZIO ORSI wrote:
> > Isn't that duplicating the information of metadata/layout.conf's
> > 'master' key-value pair [1]?
> >
> >
> > Yes, I agree that it would be duplicating that information. As a matter
> > of fact, Michał Górny pointed the same thing out.
> > However, Michał also added, quote: "What's really lacking here is
> > support for specifying dependencies via |repositories.xml|
>
> Do we need to duplicate the information in repositories.xml, with all
> the drawbacks of duplication?
>
> Can't eselect repository add the new repository, then read the 'masters'
> value from layout.conf, and add the missing repositories recursively?
That would be a significant change in behavior for eselect repository.
Currently, it does not actually sync any repos; it just manages the
config in /etc/portage/repos.conf.
next prev parent reply other threads:[~2023-06-20 17:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 20:39 [gentoo-dev] Eselect repository feature request TOMAS FABRIZIO ORSI
2023-06-20 13:44 ` Florian Schmaus
2023-06-20 14:41 ` TOMAS FABRIZIO ORSI
2023-06-20 17:08 ` Florian Schmaus
2023-06-20 17:26 ` Mike Gilbert [this message]
2023-06-20 18:07 ` Andrew Ammerlaan
2023-06-21 2:17 ` TOMAS FABRIZIO ORSI
2023-06-21 7:15 ` Andrew Ammerlaan
2023-06-21 13:40 ` TOMAS FABRIZIO ORSI
2023-06-21 13:58 ` Andrew Ammerlaan
2023-06-21 14:12 ` TOMAS FABRIZIO ORSI
2023-06-21 14:30 ` Andrew Ammerlaan
2023-06-21 14:43 ` TOMAS FABRIZIO ORSI
2023-06-21 15:07 ` Mike Gilbert
2023-06-21 15:34 ` TOMAS FABRIZIO ORSI
2023-06-21 15:41 ` Florian Schmaus
2023-06-21 15:56 ` Mike Gilbert
2023-06-21 16:47 ` TOMAS FABRIZIO ORSI
2023-06-21 17:45 ` Mike Gilbert
2023-06-21 17:59 ` TOMAS FABRIZIO ORSI
2023-06-24 17:02 ` Florian Schmaus
[not found] ` <8ef315e8-a9fe-c33a-7ab4-ef7653c10cb9@gentoo.org>
[not found] ` <CAHTSwYiXiO2OMU4A5TiunrEy+Zs+UMFwoV3wmSdEW5RNrS5xJA@mail.gmail.com>
[not found] ` <CAHTSwYgO7F2gOOSWHDOBFry4YBb1a1KSy9g8h4iUh+rK0GFRuQ@mail.gmail.com>
[not found] ` <2d264617-f48e-d129-adc2-10aac6cef2a2@gentoo.org>
2023-07-12 18:03 ` TOMAS FABRIZIO ORSI
2023-06-21 17:59 ` Anna
2023-06-21 16:49 ` Florian Schmaus
2023-06-21 17:28 ` Mike Gilbert
2023-06-21 18:42 ` Sam James
2023-06-21 19:03 ` TOMAS FABRIZIO ORSI
2023-06-21 19:16 ` Sam James
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='CAJ0EP43LeSReqT641=+TcEE=nmF2ktG3_zNoCd+zjxY65BRL7A@mail.gmail.com' \
--to=floppym@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