363200+ entries in 0.223s
ascii_field: 'I proceeded
to disassemble a Nokia 2110 battery pack, remove
the batteries, glue it
to a 6-volt lead-acid gel cell battery, and clip
the phone onto
the resulting giant battery pack (when
the battery is many
times larger
than
the phone, you don't clip
the battery onto
the phone).
The result, "Gorba's Return", has a standby
time of more
than a month.' << very spiffy, also doubles as a blunt weapon or battering ram
punkman: oh wait, didn't we do
that last month
BingoBoingo: <pete_dushenski> hmm 6 btc against
trump for republican nomination in just
the last day and a half, what are
these people on ? <<
Ted Cruz is having a moment
pete_dushenski: ascii_field "Yes, you can sell part or all of your stock anytime for a
trading commission of only 99 cents. You can also buy more of a stock you already own, or buy a new stock, for 99 cents a
trade." << ~seems~
this is
the main flesh hook,
though others include "money in your account within 3 days" and "priced at daily close"
ascii_field: l0l waitasec
they're ph0rk3d nice & proper already ?
☟︎ ascii_field: 'if it goes up, we keep
the diff' or
the like
pete_dushenski: "You pick
the stock and dollar amount.
They get fractional shares of real stock. Even kids and
teens can do it!"
ascii_field: for
t0p sc4mm1tud3,
the card ought
to have fine print
shinohai awaits mod6 's next release
to
try.
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?
ascii_field: and
the correct vehicle for all of
this is gnumake, ~if~ somebody can figure out how
to make it behave sanely when invoking makefiles recursively
mod6: ben_vulpes, mircea_popescu, asciilifeform :
thoughts on
the above ^ ?
mod6: yeah, some of
this is still up in
the air
trinque: but
that's a side note
to easy access
to
the end product.
trinque: sure, was
trying
to address ascii_field's indicating multiple build systems and so on
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.
trinque: er, with renaming it
to
the current version
mod6: it will always (until
the makefile is patched) build an output binary in bitcoin/src/
trinque: mp last night was
trying
to get someone who had no knowledge of
this stuff
to build
the
thing.
jurov: where openss/boost/etc. install
themselves
trinque: it should build in build
then crap a binary with a version string appended in
the dir you are in, imo
mod6: maybe i have amnesia, but I don't remember
that one at all.
jurov: or
that one is only
temporary?
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.
trinque notices
the shit-in/shit-out aspect of
this metaphor.
jurov: name
the output dir "sphincter"
trinque: like building
the linux kernel does with bzImage
trinque: mod6: could output where
the binary was crapped at
the end
mod6: I guess we can place a small README in bitcoin/
that can direct peeps
to rotor dir.
trinque: why rotor? is
there going
to be some other build system?
mod6: i'm sold on
that. s/build/rotor/
jurov: (and it will break all links in
teh lawgs)
jurov: and
the manifest in /shit
jurov: but if
there are compelling reasons, should not be hard
to move all versions one level down so
that you can have /shit/bitcoin/src
jurov: if you want it
to show on btc.yt , best in parent dir of src
mod6: nm. i guess in
the 'shit' dir.
mod6: so
the manifest should live in build directory as we were
talking about?
jurov: it's about having files *inside* bitcoin directory in same places relative
to each other
jurov: well,
that's kinda different
thing
mod6: <+jurov> why ask me? << don't wanna step on your
toes with golf shoes when it comes
to btc.yt
trinque: going
to make a variable :p
mod6: <+trinque> {src,contrib,build} etc ? << 'contrib' in
the sense of distfiles from say BDB/Boost/OpenSSL?
trinque: it's not as
though I'm debugging c++ at
the moment.
pete_dushenski: hmm 6 btc against
trump for republican nomination in just
the last day and a half, what are
these people on ?
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?
mircea_popescu: another
thing
that was disconcerting was having binaries in a /src dir
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.
trinque: I'll give it some love
today
then.
trinque: mod6: do you want help with any of
this? I am comfortable with my bash-fu.
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.
ascii_field: so
the
thing was something like a su version of a stream cipherator
trinque: V certainly is its own
thing
mircea_popescu: mod6 but
this manifest... wouldn't you say it's of
the nature of
the sigils ?
mod6: Because all of
those scripts need
to be re-written.
trinque: V yes, I see V
the version control system kinda being conflated with
this builder making use of V
mod6: We're a lot farther from release
than I had
thought
then.
mircea_popescu: then it'll have
to some degree be separated from what it builds
mod6: I guess I can see it
that way.
mircea_popescu: idea here is
to a degree
that V is a universal builder
trinque: does not make sense
to separate
the build system from
the
thing being built. what other project does
that?
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.
mircea_popescu: the manifest should live wherever
the rotor.sh lives neh ?
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.
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.