ATM registerurl would consider external special remotes via CLAIMURL and might then associate that URL with a specific remote.
If a remote can handle some urls (e.g. regular http) which annex can handle as well, but user wants to not associate url with that special remote, having this dedicated option would be great to have.
Note that git-annex does not store urls associated with any particular remote. The url log is simply a list of urls. This was probably not a great design choice, but we're essentially stuck with it.
So,
registerurlcan update the location tracking (which it currently does only for the web special remote and not others). But an association between url and special remote cannot be recorded by it.registerurl, besides modifying.log.weband adding URLs (with:prefix if being claimed by external remote), it also modifies.logand registers availability from web remoteThe fact that it doesn't do that currently (but did in the past) for external remotes is currently discussed in https://git-annex.branchable.com/bugs/registerurl_does_not_register_if_external_remote/
So, my desire here ATM to be able to say
registerurl --remote weband get it registered towebremote, thus to have web remote listed in .log and url added without:.What it could do is with --remote=foo, check if foo claims the url. If not, fail to register the url. The discussion in ?registerurl does not register if external remote is inclining me toward an option that works like that.
I suppose that --remote=web could, as a special case, force use of the web special remote, bypassing any CLAIMURL.
addurl --rawdoes the same thing, but it makes sense to have a plumbing level way to do that.Implemented --remote for registerurl and unregisterurl. Including the --remote=web special case.