-
Notifications
You must be signed in to change notification settings - Fork 42
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
Relative paths #280
Comments
I have logs from other patches in the same place that patched successfully. I will post them if they will help. |
In that auto-patcher has not had a problem with this before, I think I may have screwed something up seeing that it has been years and this issue never came up. I recently swapped drives and installed a fresh install of osx on CPU along with a fresh clone of autopatcher. I ran "git clone ....". Someone in xda posted it.. After I did that ran the bash.sh script. And added the auto_patcher to end of the PATHS osx file. Then ran auto-patcher ROM openpdroid from home directory. This a few weeks ago and the first patches were successfully, then when I ran it recently it did not autoupdate so I repeated a fresh auto-patcher clone like before and attempted to patch the rom... And posted the log somewhere around here. Did I leave any necessary steps out or make a mistake on my end? |
Well, I haven't added it to my system path. That is done specifically so you can call the script from any directory. But as you noticed, the script is really designed (at this point) to be ran from the directory it is already in, i.e the folder created from the git clone. We rely on some relative paths and that it what is breaking. Specifically, the log is being created from wherever you call it, and it cannot find the .config file, so it will not auto_update. You can either just I do intend to try and be a little more conscientious about all that, which is why I opened the issue. But I have a couple other things I need to solve first, if I can. |
I see that if the auto_patcher is invoked from some parent directory instead of from within the bundled directory, things like this are found
Also, it sounds like the log is then created and written to in the calling directory. This is sloppy and needs to be fixed.
The text was updated successfully, but these errors were encountered: