Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#80272 - [clang15] please add python bindings

Attached to Project: Arch Linux
Opened by M. Greyson Christoforo (greyltc) - Thursday, 16 November 2023, 20:35 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:26 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hi, it would be great if this package shipped with python bindings just like how the clang package does, only with the python module renamed to avoid conflicts. clangXX where XX is 15 in this case. I've made an AUR package to work around these missing bindings: https://aur.archlinux.org/packages/python-clang15

Thanks!
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:26 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/clang15/issues/1
Comment by Toolybird (Toolybird) - Thursday, 16 November 2023, 20:52 GMT
The cost/benefit ratio seems a bit iffy when older clangs are essentially on borrowed time. AUR is likely the better place (for my 2 cents).
Comment by loqs (loqs) - Thursday, 16 November 2023, 21:23 GMT
Somewhat related postgresql 16.1-1 in testing passes all regression tests with clang 16. openshadinglanguage is waiting for a release including [1], julia still needs llvm 15 [2].

[1]: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/1730
[2]: https://github.com/JuliaLang/julia/pull/51720
Comment by M. Greyson Christoforo (greyltc) - Thursday, 16 November 2023, 23:43 GMT
> The cost/benefit ratio seems a bit iffy when older clangs are essentially on borrowed time
That sounds like an argument against packaging any of the out-of-date clang/llvm stuff.

I think if we're going to package them, their features should match what the non-out-of-date packages provide. Including the python bindings here rather than in the AUR ensures their versions are synchronized/matching which seems good.
Comment by loqs (loqs) - Friday, 17 November 2023, 13:15 GMT
> > The cost/benefit ratio seems a bit iffy when older clangs are essentially on borrowed time
> That sounds like an argument against packaging any of the out-of-date clang/llvm stuff.
clang15 is packaged while other packages are incompatible with the clang 16 release. Similarly gcc12 is packaged but the split package only contains gcc12, gcc12-fortran, gcc12-libs while gcc contains additionally gcc-ada, gcc-d, gcc-go, gcc-objc, lib32-gcc-libs, libgccjit, lto-dump.

Loading...