Closed KaiSforza closed 11 years ago
Yeah, repo-add
actually suffers from the same problem but the recursive directory search is only making the problem more visible.
The problem is that %FILENAME%
(for repo-add
too!) is set the package's base name: /foo/bar/repo/my-package.pkg.tar.gz
-> my-package.pkg.tar.gz
, regardless of were the package actually is relative to the repo database.
Thus unless the file is actually present in the same dir, pacman won't be able to find it.
Its something I actually have to poke at. I've asked Allan last night if pacman can handle relative paths for %FILENAME%
and he basically told me its completely untested so I don't know what's the most appropriate thing to do is yet.
That said, I'll probably require a recursive find to be explicit in the near future.
Interesting. I'll have to test out some hand-made db's.
Oof. So, did some testing (edited the %FILENAME%
to point to a subdir), and it actually works if that subdirectory is present on the host machine, but pacman will not make that directory for you.
Okay, this should now be fixed. Repoman now does two things:
Error messages need some love but this issue is effectively fixed.
repoman should not be adding packages from subdirectories, only things from the current directory specified. I don't believe that pacman handles things well when there are multiple directory layers:
i3-git is in a subdirectory here.