Let's say I'm working on a PHP application and I want to integrate some PHP packages like TWIG. Using Composer or some other automated management or code assisting technologies is irrelevant here. All included packages will have the MIT license, plus a couple of packages with the LGPL license.
Let's assume I'm gonna have my own folder structure for allocating third-party packages. For this example, it will be
A regular installation of TWIG looks like this:
/doc /lib /src /test .editorconfig .gitignore .php_cs.dist .travis.yml CHANGELOG LICENSE README.rst composer.json phpunit.xml.dist
What I would like to do is to have the
src folder contents allocated in
/libraries/twig or even
/libraries/twig/twig (if I want to mimic the package naming convention onto the folder structure, so I could integrate the TWIG extensions package into something like
/libraries/twig/extensions and so on...).
But I don't know if I must retain ALL files and folders (like Composer does when you add
twig/twig as a dependency) or just the bare minimum (maybe the bare minimum plus the LICENSE file). I'm not going to modify any of the source files, just use them.
Is this possible or does this conflicts with the licensing terms for the package?