16800+ entries in 0.048s
mod6: or even give a source file name, then output all the vpatches that touch it & their before & after hashes, or something.
mod6: i should look into this
mod6: so if ascii's V 'origin' command would take a hash as a parameter then show you the vpatch where it was touched, that would be helpful.
mod6: i think that is correct
mod6: ../../../../patches/bitcoin-asciilifeform.4-goodbye-win32.vpatch:+++ b/bitcoin/src/headers.h b86114b5b74d2b9e737798f78804439c5cdd0ae42440615c57fc85cb0ac7d8b8a454d2ef44048db6af0ca00a938178173eece431b273462dbc299c1501b86600
mod6: # grep "b86114b5b74d2b9e737798f78804439c5cdd0ae42440615c57fc85cb0ac7d8b8a454d2ef44048db6af0ca00a938178173eece431b273462dbc299c1501b86600" ../../../../patches/*
mod6: ok yah, its just headers.h
mod6: oooh. hmm. maybe im looking at this wrong.
mod6: it's not just headers.h, theres a number of others.
mod6: in other news, i can't seem to get -setvernum to work either? or how can I tell that it worked?
mod6: gas here $1.55 today
mod6: we need to focus on the makefiles & the release. meanwhile im sure theres a zillion other things.
mod6: yeah, you've got some time yet before we can really dig into that in earnest anyway.
mod6: <+mircea_popescu> so in this sense mod6 it has my imprimatur that bothering to grok it isn't a waste of your finite time. << yeah, agreed, Sir.
mod6: <+shinohai> ok mod6 test completed, did not have to set set the perl option before building << ok good deal, i assume that the PERL_MM_OPT thing is an evironment deal.
mod6: i went down this road probably like in december or november or something. just was its own ball of wax.
mod6: or are you saying something different?
mod6: but anyway, if we wanna stuff all of that stuff into shit as well, then we need to hack on buildroot to not rsync it -- now we've forked our own.
mod6: well, a dozen or so ya.
mod6: but then it pulls all kinds of stuff.
mod6: oh for like the makefiles and stuff? i think we were just gonna put the stuff in the shit dir iirc.
mod6: just create a 'patches' and '.seals' dir in the same dir as v.pl and you're golden
mod6: you don't ~need~ to run the init command at all
mod6: you can do that just fine.
mod6: there suprisingly isn't ~that~ much code.
mod6: sure, there seems to be a bunch of power here in this tool - would be nice to harness that and make some useful stuff.
mod6: anyway, yeah, i feel like if we bring this thing into the fold, i aught to know what the back end is doing.
mod6: rahter than the reverse.
mod6: i think i wanna try to work from tinyscheme/shiva -> C++ interface with bitcoind -- seems a more sane way to figure this thing out.
mod6: im gonna keep reading scim see what i can figure out.
mod6: was tinyscheme a beter alt than minischeme simply because of its size and ability to fit in head?
mod6: oh, ok. was that ever repaired? or isn't updated? i thought I saw the guys comment on his website that said "until i'm dead" or something?
mod6: ah. right, with the debugging parts enabled. yeah, danger lurks.
mod6: for sure, just like you wouldn't want to expose your rpc port to 0.0.0.0
mod6: the thing thats a bit backwards is trying to learn how scheme works through the lens of C/C++
mod6: thanks for the pointers.
mod6: i gotta digest all of this a bit. heheh.
mod6: i guess that was all in scheme.h
mod6: unless im wrong about what that was doing.
mod6: saw a lot of func pointers that seem to expose an interface into the thing tho
mod6: i did dig through all of the src/shiva code too - but since im not super cluded on scheme yet, dont quite know everything thats going on there.
mod6: <+ascii_rear> mod6: see anything that doesn't make sense ? << not yet. was just poking through how you load this thing up (in src/shiva.h|.cpp) - also looking at how to define more operations
mod6: im digging through the shiva code :]
mod6: keep lookin, it all helps us.
mod6: i need to update my wot one of these days.
mod6: congrats gernika. thanks for testing & reporting
mod6: ben_vulpes: the buildroot hash is in deps/Manifest.sha512
mod6: i think his 'p' or whatever the name is, is going to do away with that -- least iirc.
mod6: i guess that may not be horribru. ask users to gather up pub keys, place in a separate dir other than .wot, import them into temp keyring, use them, and then remove the temp keyring when finished.
mod6: now, we could have automated this into a temp keyring
mod6: <+ben_vulpes> mod6: do you expect me to have korsgaard's key in my personal keyring when running build-bitcoind-V99996K.sh? << yup, this is how it works if we want to verify the buildroot package cryptographically.
mod6: which, might eventually happen.
mod6: the only real way around this is for me to write all of that stuff by hand.
mod6: i might regret the notion of using wget someday, but I figured it possibly better than writing some native code in perl that would most likely utilize some module, or even importation of the module directly.
mod6: ight hold in our minds.
mod6: <+mircea_popescu>
http://log.bitcoin-assets.com/?date=30-01-2016#1390077 << this is a bad idea inasmuch as it leaves my build process stranded, so i'll be stuck forever using current v and i suppose forever pressing 9996 then ? << yeah, i read your comments earlier on this. part of "battle-ready" to me means not only that it has lordship blessing, but it doesn't break any security paradigms that we m
☝︎ mod6: yeah, cause if you don't run the script, then you need to set up everything, including the rotor, buildroot & copying around the config, and tons of other stuff.
mod6: same as the makefiles will do.
mod6: i actually think if you follow the steps in the wiki, jurov is incorrect, you don't need to know anything about V. or download it seperately, or anything. the script does it all for you.
mod6: ofc. we'll wanna put our newb hats on and try the steps anyway tho
mod6: <+danielpbarron> what needs to be changed? just the url to the .sh ? or are some of the steps different now? << yeah, i think the steps are going to be fine, other than the URL to the new script (when we finally get it deedbotted) and the name of the script.
mod6: oh its not even in here.
mod6: oh looks like you can just pass it a dpaste
☟︎ mod6: i guess i could do the deedbot part, not sure how to work it th
mod6: danielpbarron: do you wanna update the wiki as soon as there is a get-able deedbot entry for this?
mod6: trinque can you pu'
http://dpaste.com/2VBF9V2.txt' in there (maybe run a dos2unix on it first) with a title like the other one ala 'build-bitcoind-V99996K.sh' or whatever?
mod6: but it really does need to be updated for v99996 today.
mod6: so in reality, no you don't need V or anything. i think if you just follow dpb's wiki steps it's all good.
mod6: <+jurov> even v.pl, for that matter... :) << this is available in the ML & on the foundation homepage.
mod6: we need to get that script into deedbot so we can update the wiki
mod6: ah ok. just to see if you hit that same PERL_MM_OPT thing? or just on another OS?
mod6: asciilifeform will have to confirm/deny that i used the correct patches.
mod6: yeah, we got a bunch of files that differ. but i might have built something that you haven't.
mod6: looks like our header files differ for sure.