goatherd / patch-installer Goto Github PK

As far as I can tell there is no way to enforce order of composer installation beyond the dependency tree. Regardless of which order I place my dependencies, Composer wants to install patch-installer first. Is there a way to enforce order that I'm unaware of or a way around this limitation?

squizlabs/PHP_CodeSniffer#179

How does the installer interact with composer installed PHARSs? Can it install custom bundles? Is there even an issue here?

when patches work (#1) do allow to undo them.

Need to consider various composer update types:

• vcs (git)
• archive
  others?

Since the patch may be applied to a range of target versions it might break/ be broken by updates to the patched code.

It should be documented well and in detail that using patches is applicable to only fixed versions/ tags and not ranges. That way it may be ensured to have the proper patch tag applied for any target version. Relates to goatherd/phpcs_installer/issues/5.

There may be a need to fall back to such brute force approach. It however should not be encouraged.

Although you list the 2 clause BSD license in composer.json the actual terms of the license are to be found no where, neither in the code or in a LICENSE or COPYING file. 😄