107500+ entries in 0.809s

assbot: Logged on 21-02-2016 16:27:59; asciilifeform: it is an example of everything
i stand against.
phf: once
i bootstrap entire cl you mean? (define-macro (destructuring-bind ...
ben_vulpes: to be frank,
i have no idea how this gentoo image was even built in the first place.
mod6: yaaa,
i recall this
ben_vulpes:
i figured this for more of a "half bottle of wine in a girl's butt" report. entertainment, not science.
mod6: glad
i checked or they would have been in there 2x.
phf: ben_vulpes:
i'm building it from inside Clion, so
i'm not sure how easy it is to do cmake otherwise,
i can share the diff though
phf:
i have it running in a frowned upon state. cmake, llvm, clang
mod6: so once we're happy with this build-script, etc. we cna update that wiki, then we're back in sync. then
I can take some time to get the makefiles stuff all organized.
mod6: 9 connections, there soemthing
i don't see everyday.
mod6: ah, ok good deal shinohai.
I updated the script so that it doens't even pull that .sign file. we'll just rely on the sha512 that
I hvae, alf has, and ben has.
shinohai: btw mod6
I have reproduced it again just fine this morning Deb 8 and Ubuntu 14.04
jurov: as
i said, don't mind. it's my problem,
i should not avoid dubious USE flags
mod6: maybe
i should rewrite V in C
mod6: but
i thought you said that `ls` and `pwd` didn't work, like in your shell. that shouldn't have anything to do with perl.
mod6: lemme see if
i get this. perl with thread support broke your entire gentoo?
jurov: mod6 well, on another box
i updates glibc to same version and perl works fine
mod6: jurov: fwiw,
i do a huge % of testing on a gentoo env with perl 5.20...
phf: (
i.e. no reason to corrupt db in the process)
phf: oh
i agree, it should kill, just not without prejudice
jurov: asciilifeform: how do
i list patches that went into glibc-2.22-r2 ?
jurov:
i updated glibc with the patch
jurov: why do
i keep getting such obscure stuff...
☟︎ mod6: take a look,
i've removed 3 lines: 1. in the comment section where it lists PK's key fingerprint at the top 2. the curl that pulls the sign file for buildroot-2015.05.tar.gz.sign 3. the gpg command that verifies buildroot-2015.05.tar.gz.sign
mod6: asciilifeform: not as far as
i've seen.
ben_vulpes: asciilifeform produced legacy hashes, they match the ones
i have on disk and the ones you have right?
phf: yeah, korean places are not bad, but
i know only of one that caters specifically to koreans (
i.e. good heat), a lot of them are western oriented so massage and facials and such
phf:
i hnfi. these people do "spas", but the sauna part is typically a joke
mod6: ben_vulpes: yeah,
i dunno what the deal is with it, seems to not work exactly as expected.
ben_vulpes: mod6: while there's no harm in checking the .sign,
i don't know what it buys us
phf: as soon as
i can move again,
i'm going to make it to russian&turkish baths in nyc. they don't really do saunas on the east coast, but that baths place is awesome
☟︎ kakobrekla: meanwhile
i was the only person in sauna yesterday evening
phf: kakobrekla:
i went camping in the Appalachian last weekend, -20c w/ winds, but it was awesome.
i did just enough trash talking about russian blood to come down with a flu by thursday...
mod6: anyway,
i guess
i don't mind,
i can add a part where we check the SHA1 & MD5 of the buildroot artifact and then continue to verify that .sign file.
mod6:
i think this was actually discussed quite some time ago.
i dont remember what the sentiment was exactly. but
i think it was like "meh"
mod6:
i guess, the other good news to that is you wont need to import that rando's guy's key into your keyring. still would need mine, alf & trinque's tho.
mod6: so with that build script,
i'm thinking just take out the curl & --verify of that stupid .sign file.
jurov: lol looky now
i'm the one to predict crapocalypse
phf:
i recall riastradh making an srfi proposal for a minimum subset of filesystem operations. could just implement it for tinyscheme
jurov:
i smell you'll eventually end with different presses in diff machines due to different filesystem semantics
polarbeard: yes,
I'm not surprised that you have a different point of view, and
I'm even pleased
I think
polarbeard: never,
I'm not translating trb to scheme
polarbeard: atm
I just wanted to dump what
I'm working for, to get constructive feedback
polarbeard:
I'll split the bug fixes into their own vpatches when the time comes
polarbeard:
I won't be adding unnecessary code to init.scm
polarbeard:
I'm just encapsulating the functionality
polarbeard: because
I'm marshalling per value type, not per hook type
polarbeard: re: my patches,
I'm trying to keep an up to date version of them on my github trb repo, wouldn't mind submitting to the ml if somebody asks
mircea_popescu: why'd
i guess like when talking to 16yos on saturday night ?
mircea_popescu:
i for instance judged that since you DON'T say the obvious, you specifically do not mean the obvious.
mircea_popescu:
i just don't see the gap between "cleanly covers corner cases" and "is turing complete" bridged.
assbot: Logged on 21-02-2016 06:02:08; punkman: asciilifeform: (you will have to rename the dir manually, because DIFF IS RETARDED) <<
I'll do a punkdiff release this week
mats:
i don't see why there would be a handicap now
punkman: asciilifeform: (you will have to rename the dir manually, because DIFF IS RETARDED) <<
I'll do a punkdiff release this week
☟︎