log☇︎
281300+ entries in 0.175s
asciilifeform: my point was that we actually have a handle on ~all~ the deps
asciilifeform: before the great cleansing
mircea_popescu: or was it the xwidgets w/e that thing is called ?
mircea_popescu: at some point, there actually was, iirc
mod6: I tend to agree, overall though. It should belong with trb.
mircea_popescu: eventually people will build management trees on top of this. much like phf's "make deedbot lines print out gray".
mod6: Anyway, got some time to mull it over. :]
a111: Logged on 2016-07-14 02:06 mircea_popescu: (i'm not saying you're making a mess, i'm just saying - we're stuck with all this grandfathered in bullshit, such as boost, openssh, who the fuck knows what else even. qt ffs.)
asciilifeform: http://btcbase.org/log/2016-07-14#1502685 << what has mircea_popescu been smoking?? there is no qt in trb ☝︎
mod6: I started there for sure. Once I actually did this, it works, no problem with that. Was just trying to think, "what will the tree look like in 10 years, 20 years?"
mircea_popescu: 1 thing, 1 tree.
mircea_popescu: if item x, whatever it may be, can only be used to do Y then it belongs in Y's tree
mircea_popescu: this isn't properly called cruft tho.
mod6: The thing is, they /are/ really a part of trb itself.
mod6: The one staring me in the face is this: If we place them in trb's tree, we'll be adding vpatch after vpatch to the source base to update the makefiles as they require to be updated. Having them in their own tree could elimiate cruft in trb.
mircea_popescu: it seems to me they should be in trb tree. which tradeoffs do you see ?
mod6: this really leaves one last question that has to be thought through before we move on; Do we place the makefiles into trb's tree, or do we place them in their own tree? I've thought about this quite a bit. And there are tradeoffs to both.
mod6: and the makefiles are complete.
mod6: let's fast-forward for a minute and pretend that your solution is implemented.
mod6: building up tons of technical debt that I (or someone) has to fix eventually anyway.
mod6: which isn't a bad thing; i'd rather do it slow & careful, than fast and reckless.
mircea_popescu: but hoenstly seems to be actually coming together
mod6: it'll be nice to be able to move forward from this part.
mod6: it really has been like herding cats to get all of the build infrastructure into place.
mircea_popescu: ya not the end of the world. pretty big though. see what trinqwue says
mod6: <+mircea_popescu> at least this'd allow some basis for proper management of this mess, rather than current adhocness << the nice part about the makefiles and your preposed solution is that we would finally have a solution in place for all of this.
mod6: So hopefully that'll be just fine.
mod6: <+mircea_popescu> mod6 specifically, iirc it's tens of mb not gb. amirite ? << Yes, Sir.
mircea_popescu: and in other ethedao news, today toelik butt-erin releases DA CONE! https://media.giphy.com/media/hYXKE2SGWmYIU/giphy.gif
mircea_popescu: mod6 specifically, iirc it's tens of mb not gb. amirite ?
mod6: mircea_popescu: thanks for your input here, its high time that we get away from the adhoc nature of this build process.
mircea_popescu: an you put a number on that ?
mod6: trinque: is there a max length for deeds? (just curious about the above ^, some of these might be mightly large) ☟︎
mod6: for the buildscript and the makefiles. so that makes sense.
mod6: Yeah, it certainly has to be there.
mircea_popescu: only if signed by people you trust the sigs of
mod6: Or not, and they place the deps in there by hand, on their own. Then continue building.
mod6: a person wants to build, presumably with the makefiles, but could be a build script... they pass the builder a flag that says "get these deps for me automatically", at which time, it'll go and fetch the deed(s) and verify them, decode them, and place them in the correct place and continue building. ☟︎
mod6: we make base64 encodings of the artifacts. we deedbot those, they are signed.
mod6: i think you have the same idea as i've been pondering...
mod6: mircea_popescu: yeah, for sure. i reading though the above here...
BingoBoingo: From the mines, a respite https://i.imgur.com/OrGKuRv.jpg
mircea_popescu: (i'm not saying you're making a mess, i'm just saying - we're stuck with all this grandfathered in bullshit, such as boost, openssh, who the fuck knows what else even. qt ffs.) ☟︎
mircea_popescu: at least this'd allow some basis for proper management of this mess, rather than current adhocness
mod6: Makefiles will also solve alf's complaint about "shouldn't pull these from the web at all."
mircea_popescu: makefiles also works yes. i'm thinking more in the mid term than for the next version necessarily.
mod6: one caveat here, I want this to be the last release of the build script -- so I don't wanna do any heavy lifting here. Would rather put such effort into the makefiles instead.
mircea_popescu: could have a standard disclaimer up top, have it ignore #s or w/e.
mircea_popescu: and it knows that if the flag is on, it goes to where deed so and so is and checks it, debases it, unzips it etc.
mircea_popescu: what i'm thinking is : the binary/payload in question, base64'd, deedbotted, and the build script modified to take an optional parameter to "allow deedbot import from known signatures" and then it can have a $ifdef for "buildoot"="deedbot.soandso"
mircea_popescu: yeah, it would in this instance, but it'll become unmanageable in short order. because it's not just one such item
mod6: So, a clearsigned manifest that holds the URL and the SHA512 that I attest is correct then, deedbotted?
mod6: So was thinking a clearsigned manifest could do the trick there.
mircea_popescu: hence why it'd be a deed rather than a v diff.
mod6: I'm a bit hesitant to "sign" a file outright that I don't have carnal knowledge of -- say openssl - at least without a disclaimer that says "I am only confirming the SHA512 of this artifact is ABCDEF1234... This does not mean that I have read that code and it ``fits in head''."
mircea_popescu: yeah what i;m thinking is, since this "we gotta import crap" thing is going to continue, might as well put some sort of deed process into it
mod6: I could create a clearsigned manifest that could reside on deedbot.org that could be also pulled down, verified and used.
mod6: they are not signed at this time. the build script in its current form, will pull the dep from deedbot.org and check the SHA512 against what is hardcoded into the script. if it matches, we continue, if not we die.
mircea_popescu: mod6 did you check/sign the copies ? ☟︎
mod6: Will provide further updates on the makefiles project as I have them. Stay tuned.
mod6: or maybe that was lastnight. either way.
mod6: great work! i build mine on gentoo, and seemed to work good this AM.
shinohai: built thrice mod6 Deb, gentoo, and Arch
mod6: As far as the Makefiles are concerned, we're having good success there (other than the remote sites for the deps), and will probably be making the same deedbot.org updates to that as well.
mod6: If anyone wants to test this along with us, let me know. Will provide you a link. Want to ensure that it works well before we deedbot the new build script.
mod6: So I've updated the forthcoming V99994 to pull these from deedbot.org as opposed to their respective places out in the tubes.
mod6: trinque was nice enough to host all four of the deps that we require on deedbot.org; openssl, bdb, boost, and buildroot.
mod6: so last week buildroot's site was down (for about a day) and currently the dang sourceforge site doesn't seem to be allowing curl to grab the boost lib.
mod6: shinohai: hey thanks for giving that a try!
BingoBoingo: I find it disturbing how many "people" out in the wild have no idea that natural gas piping is a subset of plumbing
a111: Logged on 2016-07-14 00:24 mircea_popescu: if they had half a brain they'd give up the pretense and go learn how to do plumbing or something useful more alligned with their intellectual capabilities.
BingoBoingo: http://btcbase.org/log/2016-07-14#1502631 << But drain/waste/vent side. Dun want those monkeys playing with natural gas and I'll do my own supply side tyvm. ☝︎
BingoBoingo: So, surveying the neighborhood after the latest round of wind thinned the tree canopy was in the right place and time to see powerline arc and catch fire
mircea_popescu: teh lady doth protest too much, when the fuck did the "modern democracies" bloc turn into such a fucking lapdog ?
mircea_popescu: june 15th : "nato runs massive baltic exercise, with little russian meddling" ; july 6th : "putin's military buildup in the baltic stokes invasion fears".
mircea_popescu: if not for hope, how would the jam-tomorrow socialism exist.
mircea_popescu: sure, sure, and then microsoft can buy it for a trillion and then etcetera.
asciilifeform: and, quite possibly, they envision it turning into $100m when 'made mandatory for legit exchanges' etc
asciilifeform: 'i have a fine portrait of the pharaoh machined from pure shitanium' 'have $1m'
mircea_popescu: clearly, they do not have even that half a brain.
mircea_popescu: if they had half a brain they'd give up the pretense and go learn how to do plumbing or something useful more alligned with their intellectual capabilities. ☟︎
mircea_popescu: asciilifeform there's relatively few addresses actually in use, you can crack their hash in a minute or two.
asciilifeform: if the blacklist peddlers have half a brain, they distribute the thing as hashes
mircea_popescu: and in other "venture capital backed entrepreneurial ideas re bitcoin aka blockchain technologees + their respective lamestream media coverage" news, http://67.media.tumblr.com/fdc9fa6c79e206b6caa9c8f1715cb2e8/tumblr_njzceuR9H71tonrdjo10_r1_500.gif
mircea_popescu: has yet to actually justify deployment.
mircea_popescu: me has had plan drawn up to include small donation to verboten list in all txn processed for what, 3years now ? as anti-this pill.
asciilifeform: presumably there is a pile of payola available to favoured sons, in this particular flavour.
asciilifeform: s is a great step … towards our goal of getting rid of any sort of illicit activity in bitcoin.”'
asciilifeform: 'Recently, the IWF provided Elliptic a database of bitcoin addresses that they identified with child porn. With this information, Elliptic can identify those illegal activities on the blockchain (bitcoin’s public ledger of transactions). James Smith, CEO of Elliptic said this regarding their involvement: “This is the first time anybody has started identifying these crimes in bitcoin and flagging them up in a system like ours. Thi
mircea_popescu: still with this ?
mircea_popescu: phf many of them not really much work beyond "cylindrical kite". light wood structure + wax paper.
mircea_popescu: asciilifeform aha, serious collection too.
asciilifeform: possibly a properly-built rotor will give same turdwise output on all boxes.
shinohai: force of habit. anyway, it built. twice
phf: asciilifeform: which reminds me, is that at linker level or assembler? because i wanted to try generating intermediate S files, and if that's where turds are, perhaps stripping them programmatically
asciilifeform: shinohai: you are unlikely to get bitwise-repeatable binary: gcc embeds turds
shinohai: ;;later tell mod6 471a2ce942966a575f00d310ed4a0be4f5f58f57d6d56caaa4bf55d7ea7e72f3f79c36f88fd84bd6f72198b5a841fb8f568c7679940d85d3030afe1fb022d0ec bitcoind
phf: we've been building kites with my girlfriend, i might pick up one of those plans for next project
asciilifeform: reminds me of ancient 'machine guns of the world' 133337 w4r3z rar, with scanz of old ink prints for same
mod6: There's maybe a few congregating spots dedicated to art, et. al. here where I'm at. Probably in most places.