Cameron Eagans

Can you please provide a complete composer.json file that will allow me to reproduce the problem?

Not presently, I'm afraid. 2.x will give you the ability to manually set your p value, though, so this issue would go away. I'm hoping to have a beta out...

Another instance of needing to specify patch depth on a per-patch basis. That's a 2.0.0 thing, and is tracked on #93.

This stems from how the plugin tries to figure out the right -p value. I'm not really sure how to make this better, to be honest, but I'll explore some...

You'll be able to specify patch depth per-patch in 2.0.0. See #93 for details on that release.

I'm not sure I understand the problem here. It shouldn't matter where package metadata is coming from (packagist.org, private packagist, satis, etc) - the patch is just slapped on after...

Ah, okay. That makes sense. I see a pretty clear way of making this work transparently in 2.x, but that's nowhere near ready for day-to-day use. To solve the immediate...

I'm surprised that it worked to specify a relative path from the future root project. I'm also surprised that doesn't work anymore. IMO, the best way to do this is...

1.x is probably where you want to go. master is the upcoming 2.0 release.

I'm not excited about supporting weird versions of patch (BSD also has one of these that's been a persistent problem). Up to this point, I've been supporting GNU Patch (which...