This repository has been archived by the owner. It is now read-only.

Lua 5.2 does not register with pkg-info #43

Closed
barraponto opened this Issue Sep 17, 2012 · 7 comments

Comments

4 participants
@barraponto

barraponto commented Sep 17, 2012

And thus building Lighttpd with lua support breaks :/
Since the Lua package has reverted to 5.1, it's all fine, but it'd be nice to try lighttpd + lua 5.2

@mistydemeo

This comment has been minimized.

Show comment
Hide comment
@mistydemeo

mistydemeo Sep 17, 2012

Contributor

Lua 5.2 no longer ships a complete .pc file. There is a make pc step, but it doesn't produce a complete .pc file.

So, not sure what to say here! Would be good to see how other package managers handle it, or if they have dropped .pc support for lua 5.2.

Contributor

mistydemeo commented Sep 17, 2012

Lua 5.2 no longer ships a complete .pc file. There is a make pc step, but it doesn't produce a complete .pc file.

So, not sure what to say here! Would be good to see how other package managers handle it, or if they have dropped .pc support for lua 5.2.

@mistydemeo

This comment has been minimized.

Show comment
Hide comment
@mistydemeo

mistydemeo Sep 17, 2012

Contributor

It looks like the Lua project considers writing the .pc to be a job of downstream packagers, not their job: http://lua-users.org/lists/lua-l/2010-05/msg00641.html

Contributor

mistydemeo commented Sep 17, 2012

It looks like the Lua project considers writing the .pc to be a job of downstream packagers, not their job: http://lua-users.org/lists/lua-l/2010-05/msg00641.html

@mistydemeo

This comment has been minimized.

Show comment
Hide comment
@mistydemeo

mistydemeo Sep 17, 2012

Contributor

Anyway, lighttpd's configure script searches for the lua-5.1 .pc specifically, so even if we installed a .pc file you wouldn't be able to use lighttpd with Lua 5.2. The solution there will just have to be "use Lua 5.1.4".

Contributor

mistydemeo commented Sep 17, 2012

Anyway, lighttpd's configure script searches for the lua-5.1 .pc specifically, so even if we installed a .pc file you wouldn't be able to use lighttpd with Lua 5.2. The solution there will just have to be "use Lua 5.1.4".

@jacknagel

This comment has been minimized.

Show comment
Hide comment
@jacknagel

jacknagel Sep 17, 2012

Contributor

Ship a pc file long enough for third-party software to depend on it, and then remove it and shift responsibility for it and that now-broken third-party software to package managers. What bullshit.

Contributor

jacknagel commented Sep 17, 2012

Ship a pc file long enough for third-party software to depend on it, and then remove it and shift responsibility for it and that now-broken third-party software to package managers. What bullshit.

@mistydemeo

This comment has been minimized.

Show comment
Hide comment
@mistydemeo

mistydemeo Sep 17, 2012

Contributor

Yeah, 10,000% agreed.

I guess lua 5.1 and the million names the .pc shipped under was a warning sign, but... argh.

For reference, this is the entirety of the output of make pc:

version=5.2.1
prefix=/usr/local
libdir=/usr/local/lib
includedir=/usr/local/include

Which isn't enough for anything to actually use it.

We could ship a .pc that's a moderately-edited copy of the 5.1 .pc. Much as I hate to encourage bad behaviour...

Contributor

mistydemeo commented Sep 17, 2012

Yeah, 10,000% agreed.

I guess lua 5.1 and the million names the .pc shipped under was a warning sign, but... argh.

For reference, this is the entirety of the output of make pc:

version=5.2.1
prefix=/usr/local
libdir=/usr/local/lib
includedir=/usr/local/include

Which isn't enough for anything to actually use it.

We could ship a .pc that's a moderately-edited copy of the 5.1 .pc. Much as I hate to encourage bad behaviour...

@Sharpie

This comment has been minimized.

Show comment
Hide comment
@Sharpie

Sharpie Sep 17, 2012

Contributor

This should probably be logged upstream as a bug.

The simple reasoning being that Lua can create a pkg-config file that works perfectly for 75% or more of all package managers. So, if 3 out of 12 systems have to modify or create their own .pc file because they do something weird, that is a heck of a lot better than all 12 systems having to repeat the same task and risk botching it along the way.

Seriously, I can't think of a single other project that is as high-profile as Lua that thinks creating .pc files is technically unfeasible and should be left to the packagers---there just isn't any reasoning or precedent for this move.

Contributor

Sharpie commented Sep 17, 2012

This should probably be logged upstream as a bug.

The simple reasoning being that Lua can create a pkg-config file that works perfectly for 75% or more of all package managers. So, if 3 out of 12 systems have to modify or create their own .pc file because they do something weird, that is a heck of a lot better than all 12 systems having to repeat the same task and risk botching it along the way.

Seriously, I can't think of a single other project that is as high-profile as Lua that thinks creating .pc files is technically unfeasible and should be left to the packagers---there just isn't any reasoning or precedent for this move.

@jacknagel

This comment has been minimized.

Show comment
Hide comment
@jacknagel

jacknagel Oct 16, 2012

Contributor

Closing, please complain to upstream (very noisily) to get them to reconsider.

Contributor

jacknagel commented Oct 16, 2012

Closing, please complain to upstream (very noisily) to get them to reconsider.

@jacknagel jacknagel closed this Oct 16, 2012

minrk pushed a commit to minrk/homebrew-versions that referenced this issue Oct 30, 2014

Merge pull request #43 from ahbeng/iterm2-beta
iTerm2 beta 1.0.0.20131124
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.