Skip to content

Conversation

AenBleidd
Copy link
Contributor

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

@AenBleidd AenBleidd force-pushed the vko_libx11_update_and_fix_crossbuild branch from 0bbd560 to c5a8b71 Compare October 5, 2025 03:22
@AenBleidd AenBleidd mentioned this pull request Oct 5, 2025
7 tasks
@AenBleidd AenBleidd marked this pull request as ready for review October 5, 2025 05:31
@dg0yt
Copy link
Contributor

dg0yt commented Oct 5, 2025

Note the port is outdated. And that version is flagged with a CVE.
https://repology.org/project/libx11/versions

@AenBleidd
Copy link
Contributor Author

AenBleidd commented Oct 5, 2025

Note the port is outdated. And that version is flagged with a CVE.

Without this flag set(X_VCPKG_FORCE_VCPKG_X_LIBRARIES ON) it's safe to keep it as is.
My first goal now to fix the crosscompilation, I can update this and all other X ports later in a separate PR.

@JavierMatosD JavierMatosD added the requires:vcpkg-team-review This PR or issue requires someone on the vcpkg team to take a further look. label Oct 6, 2025
@JavierMatosD
Copy link
Contributor

Tagging team review to see what direction is preferred here due to this port being outdated and wish CVE

string(REPLACE "ac_cv_objext=" "." objsuffix "${objsuffix}")
file(INSTALL "${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel/src/util/makekeys${VCPKG_TARGET_EXECUTABLE_SUFFIX}" DESTINATION "${CURRENT_PACKAGES_DIR}/manual-tools/${PORT}")
file(INSTALL "${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel/src/util/makekeys${objsuffix}" DESTINATION "${CURRENT_PACKAGES_DIR}/manual-tools/${PORT}")
file(INSTALL "${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel/src/util/makekeys${VCPKG_TARGET_EXECUTABLE_SUFFIX}" DESTINATION "${CURRENT_PACKAGES_DIR}/manual-tools/${PORT}" USE_SOURCE_PERMISSIONS)
Copy link
Member

Choose a reason for hiding this comment

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

I believe this is meaningless as in general we don't preserve permissions. (e.g. in binary caching it goes into a zip which stores neither Unix nor Windows permissions, only the readonly bit)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Are you sure about this? Depends on the zip library used, but zip archive itself has the possibility to store executable bit: https://github.com/BOINC/boinc/blob/be83b937e72b3ddbd6f9c81994412ec37d6d4a10/zip/boinc_zip.cpp#L84-L112
If this doesn't implemented - I can do that (technically I can also check if this is really the case, because I did rebuilt of the bunch of libraries several times with the binary cache enabled, and I haven't seen this issue, but again, need to be double checked).
If there is any other way to achieve this - please let me know because this library need to have executable bit set to make successful build.

Copy link
Member

Choose a reason for hiding this comment

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

Hmmmmm.... it's possible that the execute bit is preserved even if Unix permissions overall aren't. Would it be clearer to explicitly +x rather than USE_SOURCE_PERMISSIONS?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As for me, this is an overengineering and overcomplicating, but ok.
I'll check if that works and update this PR.

Copy link
Member

@BillyONeal BillyONeal Oct 13, 2025

Choose a reason for hiding this comment

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

Or just a comment if you don't want to do that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll do that, no problem, not a big deal.

Copy link
Member

Choose a reason for hiding this comment

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

(I originally read this as trying to do something like a system-wide install with the right permissions for a multiuser system which would be problematic as that's an explicit non-goal for vcpkg and is the origin of my 'binary caching breaks this' comment. We really Really REALLY don't want to be opening 'try to compete with apt' cans of worms and so I'm a bit paranoid when it comes to anything that may look like that if one squints. Sorry for the runaround!)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, that's completely fine, and I can completely understand you. I'm pretty much clos with the test, so I should be able to give an update of this PR within an hour.
Thank you for checking, testing, etc :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@JavierMatosD JavierMatosD removed the requires:vcpkg-team-review This PR or issue requires someone on the vcpkg team to take a further look. label Oct 13, 2025
@AenBleidd AenBleidd marked this pull request as draft October 13, 2025 23:02
Signed-off-by: Vitalii Koshura <[email protected]>
@AenBleidd AenBleidd force-pushed the vko_libx11_update_and_fix_crossbuild branch from c5a8b71 to cc6fc04 Compare October 14, 2025 00:03
@AenBleidd AenBleidd marked this pull request as ready for review October 14, 2025 00:03
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.

4 participants