public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 11:43:00 -0300	[thread overview]
Message-ID: <CAHTSwYgucLYj1VZuot-Us_mwN9C8k_frWgt9qh1ENnok5CsNoQ@mail.gmail.com> (raw)
In-Reply-To: <64a1da86-899f-56d0-4051-828716e80eda@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

>
> Sure, I think it could work.

Great to hear.
In that case I could try to give it a try and make a pull request to the
emerge --sync with a basic idea.
Any tips?
If anyone else is interested/free (I'm guessing the latter is unlikely
haha.) I'd love to have a helping hand!

Thank you for your kind responses,

Best regards,
- Tomas Fabrizio Orsi


El mié, 21 jun 2023 a las 11:30, Andrew Ammerlaan (<
andrewammerlaan@gentoo.org>) escribió:

> On 21/06/2023 16:12, TOMAS FABRIZIO ORSI wrote:
> >     In any case, this is just something to keep in mind when writing this
> >     check. It is not fully guaranteed that eselect repository can find
> the
> >     repository that is requested in some master= entry.
> >
> > Great point.
> > Btw, in your opinion, do you think having this emerge --sync + eselect
> > repository feature is doable?
>
> Sure, I think it could work.
>
> Best regards,
> Andrew
>
>
>

[-- Attachment #2: Type: text/html, Size: 1588 bytes --]

  reply	other threads:[~2023-06-21 14:43 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 [this message]
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=CAHTSwYgucLYj1VZuot-Us_mwN9C8k_frWgt9qh1ENnok5CsNoQ@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