Curtis Napier wrote:
Ciaran McCreesh wrote:
On Thu, 15 Dec 2005 22:34:05 -0500 Andrew Muraco <[EMAIL PROTECTED]>
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
