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

Handle additional unicodes #10

Merged
merged 1 commit into from
Jan 5, 2025
Merged

Handle additional unicodes #10

merged 1 commit into from
Jan 5, 2025

Conversation

mxcl
Copy link
Member

@mxcl mxcl commented Jan 5, 2025

No description provided.

@mxcl mxcl requested a review from jhheider January 5, 2025 16:01
Copy link
Contributor

@jhheider jhheider left a comment

Choose a reason for hiding this comment

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

this is fine as it stands. I'd like to see a more general implementation. at a minimum, i'd like openssl to be handled the same way, and maybe libstdcxx/libcxx. but, more specifically:

Re: unicode: I suspect we should allow duplicates in the event of non-intersecting specs for all packages, with the highest version first in CPATH/LIBRARY_PATH and only the highest in PATH. But I haven't gamed out the downsides.

intersection issues are one of the worst problems we encounter in the pantry, and we're uniquely positioned to be able to solve them in this way.

@mxcl
Copy link
Member Author

mxcl commented Jan 5, 2025

I agree, though for this initial release I just want a direct port to make diagnosing port issues easier.

@mxcl mxcl merged commit 4579cea into main Jan 5, 2025
5 checks passed
@mxcl mxcl deleted the additional-unicodes branch January 5, 2025 18:54
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.

2 participants