[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: [ANN] Stdlib 34.1 released
- From: "Gary V. Vaughan" <gary@...>
- Date: Tue, 2 Apr 2013 02:27:59 +0700
On 2 Apr 2013, at 02:14, "Gary V. Vaughan" <gary@vaughan.pe> wrote:
>
> On 2 Apr 2013, at 02:10, Gary V. Vaughan <gary@vaughan.pe> wrote:
>
>> Hi Dirk,
>>
>> On 2 Apr 2013, at 01:57, Dirk Laurie <dirk.laurie@gmail.com> wrote:
>>> 2013/4/1 Gary V. Vaughan <gary@vaughan.pe>:
>>>
>>>> Stdlib's home page is at http://github.com/rrthomas/lua-stdlib/
>>>
>>> How does one use the stuff in there?
>>>
>>> The INSTALL says:
>>>
>>> Briefly, the shell commands `./configure; make; make install' should
>>> configure, build, and install this package.
>>>
>>> I've often seen packages with that; however, this one does not have
>>> a ./configure. It does not have a Makefile. It does not have a rockspec.
>>> Instead, it has:
>>>
>>> configure.ac
>>> GNUmakefile
>>> Makefile.am
>>> stdlib.rockspec.in
>>>
>>> Obviously some package will turn these into the real thing.
>>> Doubtless some Googling or internet exploration will reveal
>>> all. But a little hint in ether the README or INSTALL would
>>> have been nice.
>>
>> Sorry about that. We've just dropped in the standard GNU INSTALL file,
>> which only holds true if you build a release.
>>
>> I'll add a note to README before the next release, thanks.
>>
>> You have several options:
>>
>> 1) Use Luarocks: luarocks install stdlib
>> That's it! This is the easiest way to get stdlib by fare.
>> 2) Use a full source release: https://github.com/rrthomas/lua-stdlib/archive/v34.1.tar.gz
D'oh! That's not a full release tarball :( I meant this url:
https://github.com/rrthomas/lua-stdlib/archive/release-v34.1.tar.gz
>> now you will have the files you need, to follow the INSTALL instructions,
>> after unpacking:
>> ./configure --prefix=/somewhere/on/your/lua/cpath
>> make
>> (as root!) make install
>> 3) Change to the release tag in your git checkout:
>> git checkout v34.1
>> proceed to step 2 above.
>> 4) Be a developer, install versions of the autotools somewhere on PATH, then,
>> autoreconf --force --verbose --install
>> proceed to step 2 above to finish now that you have the generated files.
>
> 5) when you get to step 2, and have successfully run configure, you can generate
> the rockspecs with:
>
> make rockspecs
>
> and then do a luarocks install from the local checkout with something like:
>
> luarocks make stdlib-34.1-1.rockspec
>
> or if you are not on the release branch, better to use
>
> luarocks make stdlib-git-1.rockspec
>
>
>> HTH!
>> --
>> Gary V. Vaughan (gary AT vaughan DOT pe)
>>
>
>