00:03:52  * piernovquit (Remote host closed the connection)
00:04:23  * piernovjoined
00:12:39  * Something12joined
01:20:21  * DarkGodquit (Ping timeout: 272 seconds)
02:54:28  <creationix>rphillips: so you needed luv published to luarocks?
02:54:41  * creationixis so sore from framing two full days
02:55:24  <creationix>urzds: are you around?
03:12:33  <rphillips>creationix: saw the pics nice
03:12:34  <rphillips>Yes please
03:12:47  <creationix>thanks, but I’m afraid I did the bottom layer wrong and it’s going to rot
03:13:00  <creationix>trying to find a fix that doesn’t involve three days of rebuilding
03:13:50  <rphillips>good luck
03:14:12  * creationixhopes doing just `make publish-luarocks` works
03:14:24  <rphillips>hey me too :)
03:14:29  <creationix>hmm, nope
03:15:01  <rphillips>perhaps I missed something
03:15:05  <daurn>creationix: why is it hard? :P
03:15:10  <creationix>tags are tricky
03:15:22  <daurn>no they're not?
03:15:25  <daurn>submodules are though
03:15:33  <creationix>nah, submodules I understand
03:16:30  <creationix>rphillips: ok, if I’m at luv master there is a tag at 1.7.4-5, I’ll try again
03:16:41  <rphillips>coo
03:17:24  <daurn>o.o you actually upload a 'release'? https://github.com/luvit/luv/blob/master/Makefile#L59
03:17:36  <daurn>I just use the git tag
03:19:31  <rphillips>creationix: I made a slick patch to generate portable x86 and x64 Linux builds in luvi
03:19:40  <creationix>I saw, was reading up on that
03:20:08  <creationix>daurn: that doesn’t work because luarocks hates git submodules
03:20:12  <rphillips>I assume you found the upstream project...
03:20:30  <creationix>rphillips: this one? http://phusion.github.io/holy-build-box/
03:20:35  <daurn>creationix: hence my earlier "submodules are though"
03:20:38  <daurn>;)
03:20:38  <rphillips>That is the one
03:20:53  <creationix>daurn: no, luarocks is just stupid
03:21:06  <creationix>it’s trivial to add —recursive to the clone command
03:21:17  <rphillips>luvi binary ran on all the agent buildbots
03:21:22  <daurn>I used submodules in 4 or 5 projects; they were never consistent; nor did they remove pain.
03:21:27  <daurn>these days I just use subtrees
03:22:13  <creationix>luarocks is painful for many reasons besides not supporting submodules
03:22:25  <creationix>like this whole “you need json, but we won’t tell you what that means or how to install it"
03:22:31  <creationix>and I just got “Error: API failure: nil - https://rocks.moonscript.org/api/1//check_rockspec?pac”
03:22:47  <daurn>creationix: o.o rocks.moonscript.org? how old is your luarocks?
03:22:49  <creationix>and “Warning: Your LuaRocks is out of date, consider upgrading.”, but there is no `luarocks update` or `luarocks upgrade` command
03:23:03  <creationix>daurn: just a few months old
03:23:09  <creationix>from last time I published
03:23:18  <daurn>creationix: you only get `luarocks upgrade` if you installed luarocks via luarocks (not via your distro)
03:23:37  <daurn>creationix: I doubt it; rocks.moonscript.org was deprecated over 2 years ago...
03:23:49  <creationix>I promise I wasn’t using it 2 years ago
03:23:53  <daurn>even ubuntu 14.04 has the correct url
03:24:13  <creationix>luarocks 2.2.0 btw
03:24:26  <daurn>creationix: hrm; that's just 1.5 years old.
03:24:37  <daurn>creationix: perhaps you have an old config file around tricking it?
03:25:29  <creationix>not likely, I reformat my machines pretty regularly. I think this was installed via homebrew
03:25:44  <daurn>homebrew now installs luarocks as part of the lua package
03:25:51  <daurn>you can't even install it seperately
03:25:59  <creationix>yep, I’ve seen that
03:26:08  <creationix>I reformatted a different machine last week
03:26:26  <creationix>hmm, and `brew update` is broken :/
03:30:56  <creationix>ok, did a `git reset —hard origin/master` in homebrew’s folder, that should fix any problems there
03:31:09  <creationix>now have luarocks 2.2.2
03:34:56  <creationix>rphillips:, I think I got it uploaded https://luarocks.org/modules/creationix/luv/1.7.4-5
03:35:05  <creationix>I wonder if I can somehow give you permission to publish there
03:35:07  <daurn>rphillips: https://github.com/phusion/holy-build-box#static-linking-introduces-security-problems-how-do-you-deal-with-this my answer to that is no. there is no excuse. never statically link; and I'm not letting your statically linked things near my boxes.
03:36:12  <rphillips>creationix: I did sign up for an account. Should be under rphillips
03:36:19  <creationix>daurn: then build from sourve
03:36:27  <creationix>rphillips: I don’t see a way to authorize your user though
03:36:45  <creationix>I could give you my API key, but then you have access to all my luarocks (not that it’s anything other than luv)
03:37:13  <rphillips>I'm sure they have a contributor command
03:37:13  <daurn>creationix: I usually use distro packaging; but yeah, otherwise I do compile from source; and I encourage others to do the same
03:37:22  <daurn>rphillips: I don't think luarocks does...
03:37:29  <creationix>daurn: it’s insane to make pre-built binaries that dynamically link to all the different distros out there
03:37:48  <creationix>reason #5 luarocks stinks ;)
03:38:09  <creationix>mostly I just don’t know how to use it, but it has caused me a lot more pain than good software should
03:38:20  <rphillips>holy-build-box still generates a dynamic executable. Just portable
03:39:31  <creationix>daurn: for what it’s worth, we’ve historically been faster and better at pulling security patches than the distro packages
03:39:52  <daurn>creationix: historically; sysadmins don't care about your releases unless there's something they need
03:39:54  <creationix>but yes, you’ll need to update luvit apart from your apt-get based stuff to get out updates
03:40:07  <daurn>they just run debian auto-upgrade on security critical issues
03:40:13  <daurn>and leave the box running for 5 years
03:40:20  <rphillips>if they even do that
03:40:38  <daurn>^^
03:40:40  <creationix>well, once luvit stabalizes a bit longer, we can probably get it in the distros, complete with dynamically linked dependencies
03:41:01  <daurn>you'll be in the distros as soon as a major application relies on you
03:41:03  <creationix>there are no nasty name conflicts like node had
03:41:06  <daurn>that's generally how it works
03:41:36  <creationix>luvit is deployed in production (has been for years) to a ton of machines
03:41:48  <daurn>creationix: distros don't care about that :P
03:42:05  <daurn>creationix: they will package + ship you when there is a major *application* that has a dependency of luvit
03:42:15  <creationix>I know what you mean
03:42:29  <creationix>so if weblit takes off as the next ruby-on-rails, we’re good
03:42:57  <creationix>or redis switches to luvit for it’s lua core
03:43:07  <daurn>no; more like someone creates an mpd-like daemon using luvit; which then gains a popular client that people use as their daily music player
03:44:22  * daurnchanged nick to daurnimator
03:47:27  <creationix>yay, `luarocks install luv` worked
03:49:56  <daurnimator>creationix: fix your warnings ;)
03:50:33  <daurnimator>http://sprunge.us/ZPHS
03:50:58  <creationix>wow, newer cmake?
03:51:10  <daurnimator>I set my gcc warnings to be high by default
03:51:11  <creationix>I’m on 3.3.0 on this old machine
03:51:40  <daurnimator>$ cmake --version
03:51:42  <daurnimator>cmake version 3.4.0
03:53:39  <creationix>filed https://github.com/luvit/luv/issues/197
03:53:51  <creationix>I need to get to bed, got a full day of construction tomorrow
03:54:07  <creationix>if you want to try and fix things you’re welcome
04:06:34  * Something12_joined
04:08:55  * Something12quit (Ping timeout: 244 seconds)
08:10:43  * SkyRocknRolljoined
08:26:21  * DarkGodjoined
09:09:37  <urzds>creationix: Now I am.
09:58:26  * Something12_quit (Ping timeout: 240 seconds)
10:50:44  <urzds>Can I somehow access the formatter of p()? I have a little bit of trouble finding the function definition in the sourcecode, otherwise I'd look there myself...
12:55:06  <urzds>creationix: Why was the global "exports" table to carry module meta information (instead of e.g. attaching a _luvit_export metafield to the return value of the chunk)?
13:16:37  <urzds>The verb is missing from that sentence... Fix: "Why did you chose the global ..."
13:17:42  * SkyRocknRollquit (Remote host closed the connection)
13:45:36  <urzds>Is there any date parser except this? https://github.com/dvv/luvit-date
14:51:53  <urzds>What's the recommended way to ship a one-file project and its unit test?
15:48:35  <urzds>Has anyone ever seen this? https://github.com/luvit/lit/issues/142
17:46:49  * hdmsjoined
19:54:05  * piernovquit (Ping timeout: 250 seconds)
19:54:28  * piernovjoined
20:30:46  * piernovquit (Ping timeout: 240 seconds)
20:31:13  * piernovjoined
20:45:08  * DarkGodquit (Ping timeout: 246 seconds)
21:19:56  * bjornquit (Quit: No Ping reply in 180 seconds.)
21:30:08  * bjornjoined
21:46:59  * DarkGodjoined
22:16:57  * boxofroxjoined