git - Composer - how to track changes to packages -


what's best way track (my own) changes composer packages , merge later updates packages themselves?

these changes/customizations i've made package specific given project.

i'm committing /vendor folder vcs , merging/updating changes there, imagine there's better way?

should using svn:externals or git submodules kind of thing?

there 2 options if external software use not offer feature need:

  1. offer patch included in official version able use feature wanted directly inside external software.
  2. modify way of including software feature added code, , use external software unaltered.

the third way modifying new versions of external software liking, end in maintenance hell. seem this, shouldn't.

both svn externals or git submodules additionally bad way deal this, if want use composer maintain dependencies.

so right way create package depends on external package , adds feature want. can use composer exclusively manage dependencies. maintenance easy, because dependency on external package can tied 1 single version if needed, or relaxed range of versions, long modification compatible.

should enncounter new external version incompatible modification, can create new version of package depends on new version not old one, , recreate modification. updating main software new version of modification automatically try fetch newer version of external software well, or decline install newer modification because package depends on older external version.


Comments

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

SQL: Divide the sum of values in one table with the count of rows in another -