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

cl-colors2 usage breaking a number of projects? #10

Closed
pnathan opened this issue Dec 31, 2019 · 14 comments
Closed

cl-colors2 usage breaking a number of projects? #10

pnathan opened this issue Dec 31, 2019 · 14 comments

Comments

@pnathan
Copy link
Owner

pnathan commented Dec 31, 2019

Referencing PR #8 and @xach 's comment d9b1ea3#r36624741

@guicho271828 - FYI.

@pnathan
Copy link
Owner Author

pnathan commented Dec 31, 2019

@xach - I don't maintain cl-colors2. What is the specific problem cl-ansi-text introduced - do you have a test run you could link?

@xach
Copy link

xach commented Dec 31, 2019

It's nothing directly to do with cl-ansi-text. The real problem is that cl-colors2's package name conflicts with the existing cl-colors, and some common dependency graphs now include both cl-colors and cl-colors2. For example, a number of projects' test systems depend on prove, and the projects also use the original cl-colors. When the system is loaded, both cl-colors and cl-colors2 load, causing a conflict.

Prove's dependence on cl-colors2 comes via cl-ansi-text.

I've proposed to cl-colors2 that it rename its package and the systems that require it be updated to use the new name. We'll see how that goes!

@pnathan
Copy link
Owner Author

pnathan commented Dec 31, 2019

@xach how much pain is this causing the broader ecosystem right now? If it's sufficiently painful, I can back out the cl-color2 change provisionally, and then we can restart work from there.

@xach
Copy link

xach commented Dec 31, 2019

Moderate pain. Some test systems are broken. It's early in the release cycle. I think it's better to fix the root cause in cl-colors2 at the moment. Time may change my priorities...

@pnathan
Copy link
Owner Author

pnathan commented Dec 31, 2019

OK. Looks like Cage has worked on addressing it - - https://notabug.org/cage/cl-colors2/issues/1

give me a heads up if you need me to apply a change. I have no desire to cause pain to ripple out.

@pnathan
Copy link
Owner Author

pnathan commented Dec 31, 2019

I should also note that Prove is apparently somewhat deprecated in favor of Rove - https://github.com/fukamachi/rove

@xach
Copy link

xach commented Jan 1, 2020

Ok, cl-colors2 now has the package cl-colors2 and not cl-colors. Could you update the usage of cl-colors2 accordingly?

@pnathan
Copy link
Owner Author

pnathan commented Jan 1, 2020

@xach - sure thing.

@xach
Copy link

xach commented Jan 1, 2020

The branch fixes everything for me.

@xach
Copy link

xach commented Jan 2, 2020

Oh, and it would be great if it was merged to master.

@pnathan
Copy link
Owner Author

pnathan commented Jan 2, 2020

@xach - just to confirm - you mean the PR at #11 ? FWIW it doesn't work out of the gate in the CI system, since cl-color2's CL-COLORS2 package rename hasn't been pushed to the latest Quicklisp.

Do you plan to release both at the same time? If so, I'll happily merge to master.

@xach
Copy link

xach commented Jan 2, 2020

I'll release both at the same time.

@pnathan pnathan closed this as completed in f347217 Jan 2, 2020
pnathan added a commit that referenced this issue Jan 2, 2020
Fix #10 - Change package to cl-colors2.
@pnathan
Copy link
Owner Author

pnathan commented Jan 2, 2020

@xach - you're good to go on my end. Please advise if further issues arise!

@guicho271828
Copy link
Contributor

thank you @pnathan for cleaning this up --- I could not predict these issues and I feel sorry. thank you for your work @xach too.

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

No branches or pull requests

3 participants