From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C0ED7158009 for ; Wed, 21 Jun 2023 02:18:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10322E089D; Wed, 21 Jun 2023 02:18:22 +0000 (UTC) Received: from mail-oo1-xc2f.google.com (mail-oo1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D674CE0897 for ; Wed, 21 Jun 2023 02:18:21 +0000 (UTC) Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-55e1bb2ab1aso3466715eaf.2 for ; Tue, 20 Jun 2023 19:18:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fi-uba-ar.20221208.gappssmtp.com; s=20221208; t=1687313900; x=1689905900; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=bMmrv2Q8BCgr4+1eZxTZQcqyAw9As/Exv0F420TUQ8Y=; b=tIBgB4oNIIP5Crt+6XtAozT5Gcx426EXYmm94srv/J74he3TZb8fQqsccXoGl9w6SM rlRPOqJmitqtZEPjM8h57ADluBG+kOnmku8a5SGrNl/xkKXK+dNOuhDg74e8XcPKDzt+ ugEzHBYvHkTi/KJcUiYeSiorkDuLnhZngfq5l8nPJtSXmp7Ocp8QOONoRvRY1z2Q/4Qw vFeKkwhEsxMQgTW7R/P8ZPRovMxIpItPuq1ne6sOfcb55yJiX0eErMruyrRltT9+DH94 naJPzs+Bqlxg9vsDaWkfuuuiJYEA4zHw3j93WOWz+0Foo1hlN/lJycjtfJlfUzywjlgi tLag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687313900; x=1689905900; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=bMmrv2Q8BCgr4+1eZxTZQcqyAw9As/Exv0F420TUQ8Y=; b=l2+h8u3Voplt7EH0wOLopS5/hHfZXNAROkyymFVFz4ez44rFEzRVHPZa//9d9exa6e AJ7W6XBVqabNVhJTlREX/UCUy2LurwO6WcQUInvWW/n+8UrDWbodQM5fSOh7YbFmmtvk RQKYs1SWf2s8DBMd8pMhQ4h9GFes9FPU8dlj2yDYUHrmG/1WVTSXjqL5GftyyoO5CulV RX4zCWYGufIU8W9/zk/SFrNuXCkVM6q7/fX4o+PHhzSgOgrwYb5d7NfSao/PWoA4t214 ia3JYhU2wgKn5FSdXVyhtYPglDk9zBQO3h06s9oRuX5GOPZXEXUf5PyYRg6lPT8z8fro Tx/A== X-Gm-Message-State: AC+VfDzH6hoPauXm6SWvxjKC35nfrqXnac0rzao58yyQQlrbaEUZPyPm ulA/u6qCKTR9aeB7Ft3C3eW096j/fD8sqHCOBk6T/BXWAWA8bj3OHuCAtA== X-Google-Smtp-Source: ACHHUZ7aa2yPbnpVneOaeUpFOzfoMv+xdYnAEob1vfLfWGVjWwdyMav19mOwtLGo5oAqNtTUBO6+fXpft4YZpj6RCNk= X-Received: by 2002:a4a:d451:0:b0:558:b424:8c31 with SMTP id p17-20020a4ad451000000b00558b4248c31mr4026127oos.0.1687313900182; Tue, 20 Jun 2023 19:18:20 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <30d4b57b-734f-bd42-4427-15389256e80f@gentoo.org> <703cdee8-b322-6c49-be13-efd10426ea6b@gentoo.org> <06d53584-9c50-b819-cac5-abc17249c515@gentoo.org> In-Reply-To: <06d53584-9c50-b819-cac5-abc17249c515@gentoo.org> From: TOMAS FABRIZIO ORSI Date: Tue, 20 Jun 2023 23:17:44 -0300 Message-ID: Subject: Re: [gentoo-dev] Eselect repository feature request To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000a52e4005fe9a61cd" X-Archives-Salt: 21838788-d9e4-4a7c-b0e6-1fa6c1aa4434 X-Archives-Hash: f4b028f9887a3f6cee4988fcb37cfa3c --000000000000a52e4005fe9a61cd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable A warning could be a great way of making the user aware of this situation. Having said that, if eselect repository is able to check and warn the user of a not synced overlay(ies) dependency, then the hard bit is done (Right?)= . Being able to "sync it for them" should only be a tiny extra step. That step being: "Hey, there's a dependency that you are missing. Would you like to add it? (Yes/No)" Best regards, - Tomas Fabrizio Orsi El mar, 20 jun 2023 a las 15:07, Andrew Ammerlaan (< andrewammerlaan@gentoo.org>) escribi=C3=B3: > On 20/06/2023 19:26, Mike Gilbert wrote: > > On Tue, Jun 20, 2023 at 1:08=E2=80=AFPM Florian Schmaus 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 matt= er > >>> of fact, Micha=C5=82 G=C3=B3rny pointed the same thing out. > >>> However, Micha=C5=82 also added, quote: "What's really lacking here i= s > >>> 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 'master= s' > >> 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. > > > Or maybe we just output a warning after syncing if a repository listed > in masters=3D is not enabled? Less automated, but simpler. I don't think > this situation happens very often so this is probably good enough IMO. > > Best regards, > Andrew > > --000000000000a52e4005fe9a61cd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
A warning could be a great way of ma= king the user aware of this situation.
Having said that, if = eselect repository is able to check and warn the user of a not synced overl= ay(ies) dependency, then the hard bit is done (Right?).
Being abl= e to "sync it for them" should only be a tiny extra step. That s= tep being: "Hey, there's a dependency that you are missing. Would = you like to add it? (Yes/No)"

Best regard= s,
- Tomas Fabrizio Orsi


El mar, 20 jun 2023 a las 15:07, Andrew Ammerlaan (<andrewammerlaan@gentoo.org>) escribi=C3= =B3:
On 20/06/20= 23 19:26, Mike Gilbert wrote:
> On Tue, Jun 20, 2023 at 1:08=E2=80=AFPM Florian Schmaus <flow@gentoo.org> wrote: >>
>> On 20.06.23 16:41, TOMAS FABRIZIO ORSI wrote:
>>>=C2=A0 =C2=A0 =C2=A0 Isn't that duplicating the information= of metadata/layout.conf's
>>>=C2=A0 =C2=A0 =C2=A0 'master' key-value pair [1]?
>>>
>>>
>>> Yes, I agree that it would be duplicating that information. As= a matter
>>> of fact, Micha=C5=82 G=C3=B3rny pointed the same thing out. >>> However, Micha=C5=82 also added, quote: "What's reall= y 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 recursive= ly?
>
> 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.
>
Or maybe we just output a warning after syncing if a repository listed
in masters=3D is not enabled? Less automated, but simpler. I don't thin= k
this situation happens very often so this is probably good enough IMO.

Best regards,
Andrew

--000000000000a52e4005fe9a61cd--