On Thu, May 29, 2014 at 2:38 PM, Niklas Laxström niklas.laxstrom@gmail.com wrote:
2014-05-29 20:27 GMT+03:00 Bryan Davis bd808@wikimedia.org:
What use cases did I miss? What other concerns do we have for this process?
The email subject does not cover third party users, so apologies if this is not the correct place for this.
We need to hash out the third-party issues somewhere. I suppose this thread is as good a place as any to bring up your issues.
Currently updating translatewiki.net codebase is annoying, as git does not handle files replaced with symlinks well.
I am not happy since I had to spent unplanned effort to be able install extensions via composer just a short while ago. We replace composer.json with symlink to our configuration repo, where it includes the extension we install via composer.
Ori has come up with a good solution for this issue, but that solution requires changes to Composer. To me it looks like nobody is currently working on that.
Is there a way I can expedite this fix?
I think bug 65188 [0] is the solution suggested by Ori that you are referring to. Would this alone be enough to fix the problems for translatewiki.net? More directly, is translatewiki.net using the top level composer.json file to manage anything other than extensions? In the near term is there any better work around for you (and others in a similar position) other than running `git update-index --assume-unchanged composer.json` in your local checkout to make it ignore anything that happens to composer.json?
Thank you for your efforts to bring composer support to MediaWiki. I wish the process was less rough for me.
Thanks for the thanks. :) Sorry for the pain, but you are one of the power users who helps us work out the kinks.
[0]: https://bugzilla.wikimedia.org/show_bug.cgi?id=65188
Bryan