Currently when a repository defined in mrconfig is a symlink to a directory/repository, myrepos simply ignores it and outputs "no repositories found to work on".
Debian bug #793381
Currently when a repository defined in mrconfig is a symlink to a directory/repository, myrepos simply ignores it and outputs "no repositories found to work on".
Debian bug #793381
Hi; I think that project is absolutely great. However, I was disappointed that symlinks are not supported. I, too, have fallen victim to a $HOME symlink situation, but additionally, my idea of creating a generic symlink-based "views on my repositories"-kind of structure vanished before my eyes. I really think this project could need a propper refactoring with respect to resolving symlinks with respect to BOTH path-to-configuration-file and path-to-repository. I am absolutely no good with perl, however, as I learned when trying to fix it myself the last few hours
Thank you in any case for the project, because it is a nice help already! however, proper symlink support seems a must-have to me at least for real adaption into my core setup and developing stuff around it.
Cheers! S.
I too would greatly appreciate being able to track symlinks with myrepos. (Quite often I will store the repo in a common location, but use it in several other projects via a symlinks).
This used to work, but was broken in revision 52e2de0bdeb8b892c8b83fcad54543f874d4e5b8
I made a wrapper https://github.com/tbnorth/mrls to handle symlinks, it analyses ~/.mrconfig and generates output like:
the first two lines being mr commands pointing to specific absolute paths you can copy paste to run on the relevant devices.
The third line is a list of groups, I ended up adding the ability to define groups of repos. to manage together :-}