343000+ entries in 0.217s
mod6: hanbot: alrighty,
thanks. sometimes if I don't hear anything, i just assume
the worst. heheh.
hanbot: not really. i've been fucking around
trying
to get bash
to save public key block
to file without detritus, giving up for now and just copypasting. i'll letcha know if it goes wrong,
thanks for
the cleanup note.
mod6: this
thing doesn't play nice
trying
to run it more
than one
time with old artifacts laying around.
mod6: if you
tried
to build with
this script, and something went wrong, which im pretty sure
that it did, you need
to blow everythign away (aside from your .wot dir and your keyring of course - have back ups! /me looks at people who blew away
their keys) and start over.
mod6: <+mircea_popescu> ah nm, it was
the x86 flag << yeah.
mod6: # Required Public Keys
to add
to your PGP Keyring.
These are used
to verify V, rotor, buildroot, and
trinque's patch:
mod6: # Required Public Keys
to add
to your PGP Keyring.
This are used
to verify V, rotor, buildroot, and
trinque's patch:
mircea_popescu: mod6 it's no good because it still doesn't explain WHERE
they should go. it's ambiguous between .wot and keyring\
ascii_butugychag: mircea_popescu: holy shit, shitgnomes are
trying
to pervert even greenspun's law ?!!
mircea_popescu: phf
this is worthy goal and a pretty effectual approach even if it doesn't get used for anything post-grok
mod6: as soon as i get
through
the end of
this month, a renewed emphasis will be put on ditching
this script, and getting
to a finished place with
trinque's makefiles
that'll hopefully be easier
to understand.
☟︎☟︎ phf: (all
this v
talk past few days, i decided
to sit down and grok, so Writin My Own V (tm)(c) at
the moment)
ascii_butugychag: phf: i ~would~ like
to see a maximally-granular (split into patchons) version of mod6's flow graph
kakobrekla: it brings me some satisfaction im not
the only one confused
phf: having multiple hunks in a patch modify several files at
the same
time creates a harder
transition constraint
then simple antecedent/descendent pairing, so i'm
thinking it's probably safe
to construct a graph in
terms of
transitions rather
then purely a/d.
the end result should be
the same
phf: mircea_popescu: anyway, i was speaking of how
things are right now in v.py/v.pl. a hunk
touches a file, hunks are grouped
thematically (i.e. by a single unit of meaning) in a patch. a pairing of antecedent/descendent creates a graph and in combination with
topo logical sort produces a press order
mod6: I'll change
the comment, standby.
mircea_popescu: + # You need
to have
these keys in your gpg keyring
to vertify V,
trinque's special patch, buildroot, and other stuff.
mod6: to verify V,
trinque's special patch, buildroot, and other stuff.
mod6: these are public keys
that you need in your keyring
mircea_popescu: all you should in
the .wot atm is what's in
the script, ie,
mod6: hanbot: no, sorry
this is confusing.
hanbot: oh so i don't actually need korsgaard's key in
the .wot dir
phf: v is used
to press
the source only, but
there's a bunch of shit happening outside of v, including verifying some
third party package signed by
this korsgaard guy
mod6: only in
the context of verifying
the packages signatures
phf: we've been
through
this
mod6: <+mircea_popescu>
try just korsgaard << i guess you could
try
this
mod6: place
that key on your gnupg keyring via --import
hanbot: say mod6 (or whoever else knoweth), given keys in .wot dir are
to be named by wot identity a la mod6, what am i
to name korsgaard's key, since he's not in wot?
phf: ascii_butugychag: i am speaking of vpatches, i'm starting
to grok
that mp is speaking at a different level of abstraction
mircea_popescu: for
that matter
the level of abstraction displayed justifies
the use of MAYBE
three files, otherwhise it really looks like
the guy wrote
the whole
thing on one scroll so
to speak.
mircea_popescu: i don't
think you can find anyone who both read bitcoin source and
thinks
the file split is sane.
mircea_popescu: phf well yes but using v as an ideal object vs using v as applied
to
the world's most patently deranged pile of cathair and wet noodles.
ascii_butugychag: the reason why i once suggested breaking up all patches into atomic patchons is
that right now we have a stricter
than necessary dependency flow
☟︎ phf: i
think it's relevant, but i need
to reflect how. fwiw right now
there's a bunch of vpatches
that modify multiple files at
the same
time
mircea_popescu: but
this line is i suppose not germane
to your inquiry so let's let it be.
mircea_popescu: that situation may occur, and it is a signal
that
the way code is split into files is broken and needs fixing, i guess.
phf: i remember ascii suggesting
that perhaps we should stick
to one hunk per patch, but
that's not
the case right with existing patches. if z
thematically needs
to
touch
two different files (a and b),
then both modifications are inside a single patch
mircea_popescu: this remains
true even if we go from a, b being files
to
them being blocks, or
themes, or other reasonable division.
mircea_popescu: note
that (as per discussion
today and intention
throughout) your z should really be stated as z1 a' -> a'' ; z2 b -> b'
mircea_popescu: i guess it would be a
transition graph, at least in most cases.
phf: so we have files a, b and patches x, y, z. x is genesis. y is a->a'. z is a'->a" b->b'.
the way v connects
the graph is x-y x-z y-z, i.e. patches
that have hunks
that share state for a file in before and after are connected. it is explicitly not a
transition graph, which would be x-y y-z (since you can't apply z on
top of x without first applying y)?
mod6: and upon a few others successfully building,
trinque, can you work your magic with deedbot and place
that guy in
there so its like deedbot.org/build-bitcoind-v99996K.sh or whatever?
☟︎☟︎ mod6: thanks danielpbarron -- hey please give
this a
try if you can. I figured
that you might be a good one
to simplify
the steps and up date
the wiki as soon as we get some confirmation
that all is good with
the script
assbot: Logged on 29-01-2016 19:13:35; mod6: you just need
to create a .wot dir and place keys in
there,
then (in
the same directory do
this): `./build-bitcoind-v99996.sh`
ascii_butugychag: ('boogie' is an a5-sized slate
thing
that changes colour from pressure, and has a button, press and it erases
to black. runs on
tiny watch battery.)
mircea_popescu: actually,
there's a cartoon of all
thiongs
that best illustrates what a blackboard is as a device of
thought. lemme see if i can fish it out\
mircea_popescu: anyway.
the value of
the blackboard is a sort of peripheral remanence of summary.
ascii_butugychag: i still remember
the whanging headaches i got just from sitting in front row
ascii_butugychag: but i find
that
there is something palpably... unmathematical, about 'whiteboards'
mircea_popescu: lol i always wondered why us highschoolers didn't get into
toluene huffing\
ascii_butugychag: incidentally mircea_popescu will be very pleased
to learn
that over here we have crappy ersatz american non-chalky boards
mircea_popescu: blackboard is a
thing of
thought. what's on it, less important.
mircea_popescu: it also pleases me no end some of
teh womenz have reached
that pinnacle of intellectual achievement where one's needed.
mircea_popescu: i like boards so much im actually going
to buy one just for slavegirl
training.
mircea_popescu: just like
their unruly, ill behaved irl counter... parts.
ascii_butugychag: there is, however,
the ample retardation of
the 'any
time' variant.
mircea_popescu: there is no shortcut
to resolve
the interpretation conundrum.
ascii_butugychag: is it 'magic code can come ~any
time~' or 'magic code specified in WELL-DEFINED place'
mircea_popescu: consider
the epic failuire of private messages
to gather import or relevance in
the
trb and you;'ll have a fine illustration of why multiband is retarded.
mircea_popescu: ascii_butugychag would you stop
trying
to be cute. in band signalling is
the only fucking signalling
there is, until you invent
telepathy.