Skip to content
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

prevent namespace conflicts #7

Merged
merged 1 commit into from
Apr 24, 2024
Merged

Conversation

xabbuh
Copy link

@xabbuh xabbuh commented Apr 24, 2024

With this change paragonie/easy-ecc will not be installed at the same time as mdanter/ecc to prevent conflicts with two packages providing the same namespaces.

With this change paragonie/easy-ecc will not be installed at the same time as mdanter/ecc to prevent conflicts with two packages providing the same namespaces.
@paragonie-security paragonie-security merged commit e833398 into paragonie:master Apr 24, 2024
5 checks passed
@paragonie-security
Copy link

paragonie-security commented Apr 24, 2024

Thanks, that's a good idea.

@xabbuh xabbuh deleted the patch-1 branch April 24, 2024 10:43
Comment on lines +32 to +34
"replace": {
"mdanter/ecc": "*"
},

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the * a good idea? It basically means that this package acts as a drop-in replacement for any version of mdanter/ecc which is certainly not the case.

This should be either conflict, meaning that this package and mdanter/ecc must not be installed at the same time, or we should pin the last release of the mdanter/ecc package here.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What precisely is the scenario you are worried about?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants