| 1 |
On Wed, Dec 23, 2020 at 1:21 PM Michael Orlitzky <mjo@g.o> wrote: |
| 2 |
> |
| 3 |
> On 12/23/20 12:13 PM, Jonathan Callen wrote: |
| 4 |
> > |
| 5 |
> > One way this could be done without breaking things might be to create a |
| 6 |
> > subdirectory of /usr/$(get_libdir) for each version of Lua and creating |
| 7 |
> > a liblua.a and/or liblua.so symlink in that directory pointing to the |
| 8 |
> > liblua${VERSION}.* file in /usr/$(get_libdir). Then you could simply |
| 9 |
> > point those build systems at that directory and they would still use the |
| 10 |
> > correct version. As a hack in an ebuild, you probably could just create |
| 11 |
> > such a setup in (subdirectories of) ${T}, pointing liblua.a, liblua.so, |
| 12 |
> > and lua.pc at the appropriately-versioned files. |
| 13 |
> |
| 14 |
> All of these packages are masked, so breakage isn't an issue. |
| 15 |
> |
| 16 |
> And since these hacks are needed in every package that will link against |
| 17 |
> liblua, doesn't it sound like something the eclass should be doing? Even |
| 18 |
> the CMake packages would benefit, no longer having to pass in |
| 19 |
> -DLUA_INCLUDE_DIR and -DLUA_LIBRARY by hand. |
| 20 |
|
| 21 |
Most ebuilds in the gentoo repo are either using pkg-config, or |
| 22 |
already have hacks/patches applied. Perhaps if this idea were offered |
| 23 |
earlier in the year, it might have actually helped. |
| 24 |
|
| 25 |
The versioned libdir subdirectory seems like a nice idea for people |
| 26 |
building stuff against lua outside of ebuilds. Jonathan's proposal |
| 27 |
could be treated as an enhancement at a later date. |
Archives