-
-
Notifications
You must be signed in to change notification settings - Fork 476
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
Detect and warn on "replace" at submission time #329
Comments
I had to put a solr folder, overwrite schema.xml into this folder (file is provided under doc folder) |
No I just didn't look at your PR yet because it said WIP and then it got forgotten :) Is it ready? |
@Seldaek no but you can suggest directions even if it is wip, would be helpful to avoid wrong directions, i can do it after you give me your thoughts, i don't promise anything though, i just can put the will, not necessarily the time, as Warsaw is around the corner and I may enter a job anytime if I find it 👶 |
There's really nothing wrong about replacing packages or warning, we simply need to implement composer/composer#2690 |
Not needed anymore. |
In an effort to help minimize people replacing projects inappropriately, we could detect replace in new project submissions. For example, if someone says they replace "symfony/symfony" or "guzzle/guzzle", or "illuminate/*", we could put up a nice friendly notice that it can be dangerous to submit said package as-is and that if they don't know what it means they should contact support ( irc? email? mailing list? ) to find out what it means and if it is appropriate. We could also add a checkbox to say that they understand and wish to submit anyway.
The text was updated successfully, but these errors were encountered: