[openresty-en] [ANN] lua-resty-random, lua-resty-scrypt, and lua-scrypt
0.0.1)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=047d7b3a9b8e90000504ee47c065
--047d7b3a9b8e90000504ee47c065
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Looks like you haven't used Luarocks recently because most of your
comments don't apply to recent versions. De : Brian Akins
Envoy=C3=A9 : =E2=80=8E24/=E2=80=8E12/=E2=80=8E2013 14:30
=C3=80 : openresty-en@googlegroups.com
Objet : Re: Package management site and toolchain for OpenResty (Was
Re: [openresty-en] [ANN] lua-resty-random, lua-resty-scrypt, and
lua-scrypt 0.0.1)
It's not the verbosity, it's the fact I have to rename the spec file
everytime I bump the version. It also will hapily load a version of a
module that doesn't met your restrictions listed in the spec file. (It's
been a while, but that's how it used to work.) Also, module installs are
global by default and sort of a pain to use when you wan them installed on
a per project basis.
As for npm, I only know about it from an end-users perspective - both using
and creating modules - I was just using it as an example.
