From: TOMAS FABRIZIO ORSI <torsi@fi.uba.ar>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Eselect repository feature request
Date: Wed, 21 Jun 2023 14:59:05 -0300 [thread overview]
Message-ID: <CAHTSwYh42v+hP6uw63gguaum4+81DrDHfgaBivXWEUm76n3B+A@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP43ouCx=dhm48-X+SUiCPqDDasJoOBYPtrBC1cn4ZvpsLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
>
> I think flow's idea to make the sync command configurable somehow
> would be sufficient, assuming there is demand for it.
I agree.
I'm glad Flow has their ideas straight.
By the way Flow, could you share the links of the repo/PR so that we can
follow the development along? I would love to see it! ^_^
I'm not quite certain what you mean by "module" here, but that sounds
> like unnecessary extra abstraction.
>
I think my line of thought was a bit overkill.
Not to mention that I am not that well versed (if at all)
with portage's implementation detail.
PS: I forgot to mention this in the original email, but I did file a
bug with this feature request. https://bugs.gentoo.org/907959
El mié, 21 jun 2023 a las 14:46, Mike Gilbert (<floppym@gentoo.org>)
escribió:
> On Wed, Jun 21, 2023 at 12:47 PM TOMAS FABRIZIO ORSI <torsi@fi.uba.ar>
> wrote:
> > I had not considered that possibility either. In that case, could not
> the overlay
> > dependency resolution be handled as a module?
> > Said module could be a common interface for different package managers.
> > Then, the execution of said module would be handled on a per package
> manager/sync program basis?
>
> I'm not quite certain what you mean by "module" here, but that sounds
> like unnecessary extra abstraction.
>
> I think flow's idea to make the sync command configurable somehow
> would be sufficient, assuming there is demand for it.
>
>
[-- Attachment #2: Type: text/html, Size: 2606 bytes --]
next prev parent reply other threads:[~2023-06-21 17:59 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
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 [this message]
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=CAHTSwYh42v+hP6uw63gguaum4+81DrDHfgaBivXWEUm76n3B+A@mail.gmail.com \
--to=torsi@fi.uba.ar \
--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