-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
there is no way to impose order on repositories #632
Comments
This order in the one they are would in configuration files, for example /usr/local/etc/pkg/repos/01.conf will be read before /usr/local/etc/pkg/repos/02.conf the same way the first entry in /usr/local/etc/pkg/repos/01.conf will be read before the others etc. |
I respectfully disagree. |
Ordering by file/repository name does not seem to work. On fresh install of FreeBSD-10.0 there is one repository: Unfortunately, no matter which names are used the order always matches that of |
Another thing I've noticed: contrary to I have 3 repos in this order: latest, quarterly, release. |
does it still issue? We now have priority for repository as mention in pkg.conf(5) |
fixed |
The ability to order repositories is probably not required by anything in pkg design. But this feature nevertheless could be useful for performance and administrative reasons as well as working around bugs.
Right now the remote repository databases are attached in pkgdb_open_multirepos using pkg_repos for iteration, where pkg_repos is essentially HASH_NEXT, so it does not provide any meaningful inherent order.
On the other hand, sql_on_all_attached_db uses "PRAGMA database_list;" to get list of attached databases. The pragma lists databases in the same order as they were attached.
So basically the order of attachment is propagated to order of subsequent multirepository queries.
It would be nice if the repositories were effectively sorted by some meaningful property like their name or order within a configuration file or anything else that is controllable by a user.
The text was updated successfully, but these errors were encountered: