CUPS dependency that is not present in VSCode

[Frostbyte4664]

Describe the bug VSCode does not require CUPS to run, but VSCodium does.

Please confirm that this problem is VSCodium-specific

• [x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• [x] I checked the Docs page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior:

1. Build VSCodium Apparently the ebuild just unpacks a release...?
2. Attempt to run VSCodium without CUPS installed
3. /opt/vscodium/bin/../codium: error while loading shared libraries: libcups.so.2: cannot open shared object file: No such file or directory

Expected behavior VSCodium running with the same dependencies as VSCode.

Desktop (please complete the following information):

• OS: Gentoo
• Architecture: amd64
• Version: 1.83.0.23277
• App Manager: Portage
• Sandboxed: No

[github-actions[bot]]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

[arthurzam]

This is still relevant, and just closing it won't fix the issue.

Stale bots never help fix issues, they just increase the rug. https://nostalebots.xyz/

[daiyam]

stale != closed

[daiyam]

The issue is most likely due to gentoo packaging. Feel free to make any PR if needed 😉

[daiyam]

This is still relevant, and just closing it won't fix the issue.

Stale bots never help fix issues, they just increase the rug. https://nostalebots.xyz/

I most agree to the argument and I hate those that close and lock an issue after a month of inactivity.

So I've implemented loose rules:

• stale after 180 days (6 months) of inactivity
• then closed after 30 days of inactivity
• then locked after 90 days of inactivity

I found myself re-evaluating an issue after the stale notification.

[daiyam]

@arthurzam Have you opened an issue on Gentoo/Portage? It might be an issue due to the repackaging?