New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer Status Support for Non-VCS Packages #5500
Comments
how would you check whether a file has been edited for packages installed from an archive ? |
Comparing against the files in the archive. I can imagine that requires implementation per archive format. |
And this requires downloading the archive to compare (with the hope that this archive is still in the cache) |
Yes, something along those lines. So this must be a switch as it could result in quite some network cost. |
Seems like a huge waste of time to me :-) Too much effort and complexity for something that holds very little value and will most likely almost never be used. |
I agree that it's not really reasonable and not worth implementing. If you want change tracking make sure you use the preferred-install config to force source installs (this can be turned on for some packages/vendors only) :) https://getcomposer.org/doc/06-config.md#preferred-install |
Yes I know about source installs, in my scenario, that's not the context however. Anyway I can see this is plugin material. Thanks for all the feedback and tips again. |
From what I could quickly checked on the command-line, the
composer status
does not show any changes with non-vcs (git) repositories, is that correct?If so what would be your feedback about the idea to have some check or flag to verify archived packages as well?
The text was updated successfully, but these errors were encountered: