From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1En7d0-0004KO-Vn for garchives@archives.gentoo.org; Fri, 16 Dec 2005 04:55:35 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBG4sq7F003384; Fri, 16 Dec 2005 04:54:52 GMT Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBG4r2Z6004888 for ; Fri, 16 Dec 2005 04:53:03 GMT Received: from [192.168.0.165] (really [68.168.137.100]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051216045301.OIUD4477.mta11.adelphia.net@[192.168.0.165]> for ; Thu, 15 Dec 2005 23:53:01 -0500 Message-ID: <43A2482A.3080708@leetworks.com> Date: Thu, 15 Dec 2005 23:52:58 -0500 From: Andrew Muraco User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051102) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Multiple Repo Support References: <43A235AD.6030604@leetworks.com> <20051216035630.2b005138@snowdrop.home> <43A23FC7.3010801@gentoo.org> In-Reply-To: <43A23FC7.3010801@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: d7eaae5c-13c6-4c9f-98df-2f0f12f793d1 X-Archives-Hash: 88b49e7312de4e4f2fc6ea9a7c9d5e8c Curtis Napier wrote: > Ciaran McCreesh wrote: > >> On Thu, 15 Dec 2005 22:34:05 -0500 Andrew Muraco >> wrote: >> | 2. What choices/options are on the table for this feature? >> >> The big controversy seems to be over whether repositories carry a >> unique identifier string (for example, in metadata/repository_id) or >> whether it's user-assigned. The former is clearly the more sensible >> option, since it lets you do things like (syntax made up): >> >> DEPEND=">=foo-bar/baz-2.1::ciaranmssekritrepo" >> >> which would add a restriction that only packages in ciaranmssekritrepo >> would be considered. This only works if the repository knows its own >> identifier, however... >> >> Incidentally, the ::repo syntax (or whatever) would also be useful in >> the world file, along with :slot. So something like: >> >> foo-bar/baz:2::ciaranmssekritrepo >> >> would tell the package manager that you want baz SLOT 2 from >> ciaranmssekritrepo. >> >> *shrug* But it seems the Portage guys want repository names to be >> user-assigned, which makes them far less useful. >> > This functionality would come in very very handy. Would user assigned > repository names be able to mimic this functionality somehow? What about giving each repo an identifier? That way repos with ebuilds can have the repo_id in the ebuilds and not have to worry, repo_ids would take precedence when in conflict. Identifiers would just be provided for user-stuff, like ex # emerge sync MyRepo or # emerge -av MyRepo://foo ? [foo being the name of a package in repo tree with the identifier of MyRepo] what about having a portage config file /etc/portage/repositories: priority MyRepo,gentoo repository { identifer = "gentoo" rsync= "rsync://../" repo_path= "/usr/portage" } repository { identifer = "MyRepo" rsync= "rsync://../" repo_path= "/usr/MyRepoTree" } (an example for someone that wants to have MyRepo be prefered over gentoo tree) Just tossing out ideas, Andrew Muraco -- gentoo-dev@gentoo.org mailing list