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

[xlnt] update to 1.6.0 #41529

Open
m7913d opened this issue Oct 12, 2024 · 2 comments
Open

[xlnt] update to 1.6.0 #41529

m7913d opened this issue Oct 12, 2024 · 2 comments
Assignees
Labels
category:question This issue is a question

Comments

@m7913d
Copy link

m7913d commented Oct 12, 2024

Library name

xlnt

New version number

1.6.0

Other information that may be useful (release notes, etc...)

As discussed in issue tfussell/xlnt#748, the main repo of xlnt has been unmaintained for several years.
In order to continue this great project started by tfussell, the xlnt community has created a new repo to support further development by the community.

We are planning to release a new version (1.6.0) soon, mostly containing bug fixes and support for the latest toolchains. The changes are source-code backwards compatible with the 1.5.0 xlnt release of tfussell.
I'm already posting this issue now, to be able to take your feedback into account, before actually releasing the new xlnt version:

  • Would you accept a repo switch from tfussell to xlnt-community, as the original repo is unmaintained? Advantage of reusing the xlnt port in vcpkg, is that all vcpkg users automatically gets the updated version.
  • Or should we create a new port?
@m7913d m7913d added the category:port-update The issue is with a library, which is requesting update new revision label Oct 12, 2024
@MonicaLiu0311 MonicaLiu0311 added category:question This issue is a question and removed category:port-update The issue is with a library, which is requesting update new revision labels Oct 14, 2024
@m7913d
Copy link
Author

m7913d commented Oct 26, 2024

@MonicaLiu0311 Any update on how we should proceed to update the xlnt package in vcpkg? Or wouldn't you accept a new version from a cloned repo, even if the original repo is unmaintained?

@MonicaLiu0311
Copy link
Contributor

Sorry to keep you waiting, the team is in discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:question This issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants