Closed 0xced closed 8 years ago
Ha, I should have looked at the pull requests first, #461 implements pretty much the same heuristic! But this pull request adds better error messages in addition to this new heuristic.
Ha! It's really close to what I was doing with #461 indeed :)
In particular, I'm a bit worried that in your case
My bad, did not see https://github.com/alcatraz/Alcatraz/pull/471/commits/e8390db498df4917a0847df1576ba2424f93d90b πinstallNameFromPbxproj:
did not change that much (in contrast to https://github.com/alcatraz/Alcatraz/pull/461/commits/efd7888ae00ec081888d70b81e8afbe583ff4d5d#diff-b22b9cdae9c200d1c9d03235e2928944L148). But then it's not fresh in my mind, so maybe this works fine π.
Anyway, appart a few things (I'll comment inline), I'd be ok to merge your PR instead of #461 (if it's tested against all packages π).
I'd be ok to merge your PR instead of #461 (if it's tested against all packages π).
Iβm not sure if you are serious or not. I donβt think testing against all packages will bring value. This PR is about getting more packages to install. If some are still failing to install after this PR is merged, we should handle the issues on a per package basis IMHO.
@0xced So sorry if I wasn't clear. I am serious, but the goal is to ensure that we don't break the install process for the plugins which are already working today.
If some are still failing to install after this PR is merged, we should handle the issues on a per package basis IMHO.
Agreed!
the goal is to ensure that we don't break the install process for the plugins which are already working today
I took care of keeping the current behaviour of returning the .xcodeproj as soon as found if it has the same name as the package, so the risk of breaking existing packages is extremely low.
Thanks for the contribution @0xced! πΊ
π when @guillaume-algis is ok to merge
I hacked together an ugly script to install all packages on my machine. Will report tomorrow on the findings. Thanks for your patience @0xced!
If anything, it would be nice to make sure that we install more packages correctly this way
After merging this PR, the following packages will install correctly instead of failing:
This does not break any plugin which previously installed, as expected π
Full report here: https://gist.github.com/guillaume-algis/1da584f0964e94803056782394137e6e
One final thing before merging: I think this deserves a minor version number bump, not just a patch (I consider this to be more than just a bugfix), wdyt? 1.2.0
?
Great! Looks like a good improvement then. I agree on the version bump.
π
Hi @0xced, would you mind amending https://github.com/alcatraz/Alcatraz/pull/471/commits/47c562b70e35eccf59ac87feb3747e74260151ed with 1.2.0
instead of 1.1.19
and rebasing your branch onto master so we can merge this? π»
Thanks!
Done.
@jurre @kattrali @supermarin what do you think? LGTM?
Thank you @supermarin!
@0xced do you mind rebasing on top of master once more? Thanks!
Sure, I just rebased.
:+1:
Ugh. We need to re-approve. @supermarin ?
Edit: And the comment-parsing by pullapprove doesn't seems to work for some reason. I approved manually on pullapprove.com π€
Thanks @jurre ! π
Thanks @0xced and @guillaumealgis :)
The "Make the Mac Great Again" plugin would not install because Alcatraz assumes that the .xcodeproj has the exact same name as the package. This may not be true, for example "Make the Mac Great Again" xcodeproj file is "MakeTheMacGreatAgain.xcodeproj" (without the spaces).
This new heuristic searches for all .xcodeproj and works fine if only one exists in the cloned directory.
I also refactor error handling for better diagnostics when things go wrong.