pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2015-02-16	Put back autodetection of LUA_VERSION_REQD based on the package name.	jperkin	1	-1/+11

2015-02-01	revert "Auto detect lua version from required package name.",	obache	1	-11/+1
	proposed/discussed is required for such changes.
2015-01-17	Add support for Lua 5.3.	alnsn	1	-6/+12

2014-12-07	Auto detect lua version from required package name.	obache	1	-1/+11
	resolve PR pkg/49318
2014-05-03	Multiversion support for Lua.	alnsn	1	-1/+16

2013-11-05	Fixes missing ":"	obache	1	-2/+2

2013-10-30	LUA_PACKAGE is defined for build, not LUAPACKAGE.	obache	1	-2/+2

2013-10-30	make sure varable is defined before using it.	obache	1	-2/+2

2013-10-30	Reimport lang/lua as lang/lua52, and bring back the previous Lua 5.1	dholland	1	-0/+130
	package as lang/lua51. I've adjusted the depends and switched the PKGNAMEs but these packages are otherwise unchanged. This means that you can't install both at once. There are preliminary patches for that (see tech-pkg) but they aren't quite ready yet. This also doesn't include agc's builtin.mk, although it should be possible to drop it into the lua51 package with only very minor modifications. I don't think the builtin packages will allow having one builtin.mk for both lua51 and lua52, but I'd be happy to be shown wrong about that. Add infrastructure support for Lua module packages (including multiversion support), application packages written in Lua, and a redirecting bl3.mk file for packages that just link Lua in. This is based on the Python infrastructure. The new variable LUA_VERSION_DEFAULT picks which Lua package you get by default; it is set to 52 so as to maintain the status quo. Packages can set LUA_VERSIONS_ACCEPTED and/or LUA_VERSIONS_INCOMPATIBLE. I have found (I think) most or all the packages that don't work with lua51 and will be marking those; I have not tracked down most of the ones that don't work with lua52 yet as I was originally intending to roll back to 5.1 as the default.