| Summary: | media-libs/libjpeg-turbo has no option for libjpeg v7 or v8 API/ABI emulation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Byron Lathi <bslathi19> |
| Component: | Current packages | Assignee: | Codec Project <codec> |
| Status: | UNCONFIRMED --- | ||
| Severity: | minor | CC: | floppym, mgorny |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Byron Lathi
2023-06-02 11:50:58 UTC
I don't think implementing this as a USE flag on libjpeg-turbo is a good idea. Changing said USE flag would break compatibility for reverse deps, and would require them to be at least be rebuilt. Some reverse deps might not even be compatible with the libjpeg 7/8 API. It might make more sense to provide a slotted package that can install libjpeg.so.62, libjpeg.so.70, and libjpeg.so.80 concurrently to support pre-built binary packages like Efinity. (In reply to Mike Gilbert from comment #1) > I don't think implementing this as a USE flag on libjpeg-turbo is a good > idea. Changing said USE flag would break compatibility for reverse deps, and > would require them to be at least be rebuilt. Some reverse deps might not > even be compatible with the libjpeg 7/8 API. > > It might make more sense to provide a slotted package that can install > libjpeg.so.62, libjpeg.so.70, and libjpeg.so.80 concurrently to support > pre-built binary packages like Efinity. That makes sense, that’s pretty much how I am doing it now. I have the regular package installed and then compiled a separate version with the needed flags that I symlink into the install directory. Just please use separate packages, not slots. Slots are a recipe for disaster. |
