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 B17C2158009 for ; Wed, 21 Jun 2023 07:15:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AA062E08A0; Wed, 21 Jun 2023 07:15:31 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 5E470E088B for ; Wed, 21 Jun 2023 07:15:31 +0000 (UTC) Message-ID: <0b36b5e7-bb3f-2166-bb16-2fef8f35fde6@gentoo.org> Date: Wed, 21 Jun 2023 09:15:26 +0200 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 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 To: gentoo-dev@lists.gentoo.org References: <30d4b57b-734f-bd42-4427-15389256e80f@gentoo.org> <703cdee8-b322-6c49-be13-efd10426ea6b@gentoo.org> <06d53584-9c50-b819-cac5-abc17249c515@gentoo.org> Content-Language: en-US, nl-NL From: Andrew Ammerlaan Organization: Gentoo Linux Subject: Re: [gentoo-dev] Eselect repository feature request In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 11225992-b83b-4432-bfa6-5f8f94a895c9 X-Archives-Hash: d73fae2416537765357dda13e57af917 On 21/06/2023 04:17, TOMAS FABRIZIO ORSI wrote: > 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 What I meant is that emerge --sync/eix --sync does this check instead of eselect repository. To me this makes sense since we can only do this check *after* syncing. Plus the user can also make changes to repos.conf without using eselect repository, having the check done post-syncing covers these cases as well. You're probably right that once we have some message that says "Warning: {repo1} is missing, it is required by {repo2}" it should be trivial to call 'eselect repository enable {repo1}'. This however would require that profiles/repo_name is always equal to the name entry in repositories.xml, I'm not sure if this is currently always the case. Best regards, Andrew