Repository navigation
Cleanup on aisle vendor #157
Description
Activity
Related to this, what is the goal of building in user home directory ?
Using any temporary directory will be fine (and usually temp have auto cleanup feature)I understand composer use
~/.composerfor global Installation, commands in~/.composer/vendor/binare usableRelated to this, what is the goal of building in user home directory ?
See ThePHPF/pie-design#26 - TLDR, it will help us to auto-upgrade extension in the future, e.g. just running
pie updatewill be able to update all the currently PIE-sourced extensionsI understand the need to store some metadata (pie.json), but not the build
I understand the need to store some metadata (pie.json), but not the build
That is just how Composer works - you give it the path to
composer.json(although we call itpie.jsonto avoid confusion) and it does the lock/vendor stuff itself. The key files we actually want to keep ispie.json,pie.lock, but we also needvendor/composer/installed.json, since the latter file is the one that actually has the build metadata.
After discussing with @derickr a bit, everything in the PIE working directory
vendorexceptvendor/composer/installed.jsonis mostly just taking up space. It isn't used as a cache for subsequent (re)installs, so it is just taking up space.Apparently Datadog ext is very large, so this could become problematic if we don't clean up. I imagine some kind of post install cleanup step can run that removes
vendor/*(exceptvendor/composer), could work, although I need to investigate viability and impact.