18400+ entries in 0.023s
mod6: i think they both do it.
mod6: lol, we seriously need our own paste mech that doesnt do that.
mod6: oh maybe it was dpaste that added 'em in or w/e
mod6: <+trinque> thestringpuller: the script had dos line endings, which is why in recent logs I mentioned running it through dos2unix << wat?
mod6: anyway, thanks all. good talk. bbs.
mod6: or something to that effect. we can cross that bridge later.
mod6: and beyond this with V, if we create a 'Compact Disk' of all of this, we can just stick the trinity of turds in 'shit' along with buildroot and whatever it needs.
mod6: does this all sound okie dokie then?
mod6: They will be mirrored on thebitcoin.foundation.
mod6: so i think jurov has a good question; if we don't drop the turdballs into V, which we're not, and the MANIFEST is the only thing in the 'shit' directory that is pressed out by 'V', where do the tarballs come from?
☟︎ mod6: we're not going to do that, we're just gonna create a manifest with their proper SHA512 hashes.
mod6: "these" as in 'V'-ifiy the turds?
mod6: then the build script can move that stuff over as needed?
mod6: <+jurov> oh it's going to be all unpacked there? << yeah, perhaps not. currently i extract & build all that stuff under 'rotor'. i guess shit should just be: <+jurov> "The shit: BDB, Boost, OpenSSL & the MANIFEST for turds" <- this stuff the turdballs and the manifest.
mod6: they'd be like: bitcoin/shit/openssl/ bitcoin/shit/bdb/ bitcoin/shit/openssl/ or are you saying something different about splitting jurov ?
mod6: i guess it could/might have to -- this alteration will change the way we build everything currently.
mod6: i stamp out a seal.
mod6: i like the idea of a seal in that example though, because its like an official embossment.
mod6: i think 'build' is sort of non-ambigious
mod6: i think since that post, we talked about changing 'build' to 'rotor'. thoughts?
mod6: i need to get up to speed on ADA
mod6: was just digging in there punkman
mod6: to make it 'v'-ifiable we basically need to write our own.
mod6: haha, 1 month of standby time
mod6: <+ascii_field> the obj crud still ends up in bitcoin dir << yeah, but if we were to copy out the binary somewhere, any thoughts on where it should live?
mod6: ben_vulpes, mircea_popescu, asciilifeform : thoughts on the above ^ ?
mod6: yeah, some of this is still up in the air
mod6: if we don't create a bin dir for it to live in.
mod6: i'd say maybe just copy it up underneath the bitcoin dir. so: /.../bitcoin/bitcoind
mod6: no reason to change that imho
mod6: i'd like to leave the bin the same name.
mod6: oooh jurov yeah, ok. now i remember.
mod6: it will always (until the makefile is patched) build an output binary in bitcoin/src/
mod6: maybe i have amnesia, but I don't remember that one at all.
mod6: maybe bitcoin/bin ?? not sure on that.
mod6: <+trinque> mod6: could output where the binary was crapped at the end << hmm? the makefile will drop the binary in 'bitcoin/src/' -- but yeah, could be copied somehere.
mod6: I guess we can place a small README in bitcoin/ that can direct peeps to rotor dir.
mod6: i'm sold on that. s/build/rotor/
mod6: nm. i guess in the 'shit' dir.
mod6: so the manifest should live in build directory as we were talking about?
mod6: <+jurov> why ask me? << don't wanna step on your toes with golf shoes when it comes to btc.yt
mod6: that would be pretty hilarious actualy.
mod6: better ask juorv ;)
mod6: 'dist' would be fine with me. i see no problem with 'contrib' either.
mod6: <+trinque> {src,contrib,build} etc ? << 'contrib' in the sense of distfiles from say BDB/Boost/OpenSSL?
mod6: just because that makefile can get a bit hairy. but we can put it on the list.
mod6: yeah, i'd vote to change that at a different time.
mod6: oh the output binary for bitcoin?
mod6: in this case, the order of operations when building: press out a V 'branch', cd to the build directory (or somewhere in the pressed out tree), kick off the building of buildroot & everything.
mod6: but there's a fair chunk of stuff to do there.
mod6: so i can see having a say, /.../bitcoin/build/ directory or something where the scripts/config files for buildroot/and everything else/ exist and can be pressed out.
mod6: anyone in my wot in L1 can contribue.
mod6: <+mircea_popescu> mod6 but this manifest... wouldn't you say it's of the nature of the sigils ? << im not sure i understand this.
mod6: Because all of those scripts need to be re-written.
mod6: We're a lot farther from release than I had thought then.
mod6: I guess I can see it that way.
mod6: <+mircea_popescu> the manifest should live wherever the rotor.sh lives neh ? << I would argue that all of these scripts would live outside of bitcoin source V tree.
mod6: but it'll also have to be grabbed by the release vpatch so it gets included.
mod6: the interesting part about dropping in a manifest file is that i'll be off on its own as its own root and its own leaf since it'll have no decendents or antecedants.
mod6: so those would be the last 2 things that would go into V itself.
mod6: and probably can post the release vpatch to the ML also.
mod6: this weekend I'm thinking that I can get that done, and droped into the ML & V, etc.
mod6: the rotor is out of the scope of that part.
mod6: anyway my question to ascii_field, jurov, et. al. is: given we create a manifest, where should it live in the context of the bitcoin source tree itself
mod6: but this could change.
mod6: <+mircea_popescu> my personal ideal would be that ALL directories involved in this without exception are spawned as subdirs of whatever current dir the script ran in. << this makes sense. right now you end up with /.../rotor/ and ~/.wot, and ~/.seals iirc.
mod6: it basically just grabs all of these different things and then pieces it together.
mod6: the whole way that the 'orchestra' gets built, has to be that way for this minute. but certainly can change going forward.
mod6: and the subsequent commands would just do something like `./v.pl p TEST2 vpatchnameforhead wd /.../rotor/.wot` or something.
mod6: in the context of the script, it'd have to be altered in the script to say place the .wot in .../rotor so you'd have /.../rotor/.wot/
mod6: no, .wot can be wherever you want it to be.
mod6: this Manifest we're talking about creating would need to fit somewhere in the directory structure of bitcoin itself, if it is to be 'v'-ified.
mod6: Is that what you're asking?
mod6: currently, what is required is that you execute the rotor+V+TEST2 script that I wrote, and then it'll create a 'rotor' dir in that present working directory. then you'll end up with like: rotor/TEST2/bitcoin/src/
mod6: should we place that file in the 'bitcoin' dir, or any thoughts on where this file should reside?
mod6: i think he said he did anyway
mod6: is that one Mr. P.'s node? i seem to remember maybe that one was stopped or something? asciilifeform /just/ updated Zoolag and Bucephalus
☟︎ mod6: are you trying to sync against a single node?
mod6: <+danielpbarron> yeah appears so << did the whole thing build for you alright?
mod6: Sorry to hear that phf.