Description of problem:
reposync --help says it will download to "current dir".
"reposync -n -r updates" however downloads to "./$(repoid)"
I.e. documentation doesn't match behavior.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.reposync -n -r updates
Downloading to ./updates
Downloading to .
I can't find downloading to ./repoid to be useful, because this imposes
(invalid) assumptions on a user's filesystem layout.
it's being downloaded to a subdir named repoid b/c it is possible to run:
reposync -r foo -r bar
if we just downloaded to cwd w/o a subdir then all the packages would be in one
dir and you wouldn't be able to know which came from foo and which from bar.
This isn't a bug, it's an intentional design choice.
(In reply to comment #1)
> This isn't a bug, it's an intentional design choice.
Well, ... a very questionable design, or at least a fairly under-documented
More generally speaking, then reposync is not the tool I was looking for:
I am actually looking for is a tool to sync /var/cache/*/packages, and tried to
apply reposync for this. This current design forces me to resort to a tree of
symlinks to /var/cache/*/packages instead of being able to
reposync -r xxx
which I had expected to work.
Even better would be a tool similar to reposync which directly downloads to