<othx>
peepsalot: 36 seconds ago teepee tell peepsalot hello...
<othx>
peepsalot: I'll pass that on when kintel is around.
<peepsalot>
thx teepee
<linext>
damn imgbb.com is down
<linext>
my vanilla imgur
teepee has quit [Remote host closed the connection]
teepee has joined #openscad
<JordanBrown[m]>
teepee InPhase and anybody who cares: I'll be out for most of the next week, checking in only very sporadically.
LordOfBikes has quit [Ping timeout: 268 seconds]
teepee_ has joined #openscad
teepee has quit [Ping timeout: 255 seconds]
teepee_ is now known as teepee
<teepee>
JordanBrown[m]: ok, we'll try to not break too much meanwhile :)
LordOfBikes has joined #openscad
kintel has joined #openscad
<kintel>
I'm around, tell me what I missed
<othx>
kintel: 1 hour, 30 minutes, 50 seconds ago peepsalot tell kintel i may have been the most recent one to mess with icons etc, from this PR https://github.com/openscad/openscad/pull/4196
<peepsalot>
yes I think "-nightly" or "" are the only options
<kintel>
Yeah, I like that patch as it moves logic out of the code
teepee has joined #openscad
<peepsalot>
:)
<kintel>
I'm on a suffix hunt right now, looking through all the build scripts :)
<peepsalot>
so the qrc.in files specifically use the define "SUFFIX_WITH_DASH"
<kintel>
yeah, but it's a bit scary that SUFFIX is passed to CMake from each build script, without any value checks. Makes it hard to trust..
<peepsalot>
yeah i'm sure it could be made cleaner overall
<kintel>
I'll likely end up doing a one-liner, once I understand it ;)
<teepee>
I think it's 2 separate features that have evolved to mean pretty much the same
<teepee>
I think the snapshot stuff came from the windows builds and the suffix is for the debian packaging
<teepee>
with the introduction of the icon and other data switching things started to get fixed regarding possible values
<teepee>
while it might be useful to have some free-to-use suffix, e.g. for people who would want to build their own non-conflickting packages
<teepee>
I'n not aware of anyone doing that, so I suppose dropping that possibility and simplifying things should be fine
<InPhase>
othx: tell othx self-awareness has been obtained.
<othx>
InPhase: I'll pass that on when othx is around.
<teepee>
oh my :)
<teepee>
botsnack!
<othx>
YUM! This is why I love #openscad.
<teepee>
nice, we need a second bot for them to play message ping-pong
<InPhase>
Someday 2 years from now perhaps an error brings two of them online. :)
<InPhase>
JordanBrown[m]: Enjoy your whatever you are doing. Sorry I didn't get around to evaluating the object PR yet. My holiday plans shifted under my feet on me, and I lost that time I was planning to put into that this past week. I still intend to do it, and still think it's important. :)
<JordanBrown[m]>
Anime isn't really my thing, but a close friend is running their registration desk and asked me to help... and they run software that I wrote, and this is only about the fourth or fifth time it's being used.
<JordanBrown[m]>
I don't think I've yet encountered anybody who couldn't *read* it. (Then again, if they couldn't read it, would they comment?)
<JordanBrown[m]>
Whether they could *write* it is another question entirely.
<JordanBrown[m]>
Of course, I'm 61 and I probably couldn't write it. I learned cursive in the 3rd grade or so, and stopped using it as soon as I could, which was something like the 6th grade.
<JordanBrown[m]>
And if you don't "get" the second one, it means you haven't looked at it enough. It's one of my favorites.
kintel has joined #openscad
<kintel>
Turns out that while we export SUFFIX from all the Circle CI builds (except macOS), we never actually pass that on to CMake..
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #openscad
<kintel>
Anyway, after reading all the scripts and code: SUFFIX and SNAPSHOT are orthogonal concepts. I'll fix up the scripts to make snapshot builds use the nightly icons, but leave the SUFFIX stuff alone for now
<teepee>
I'd say disable / drop support - only appimage needs to be updated
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ur5us has joined #openscad
califax has quit [Ping timeout: 255 seconds]
califax has joined #openscad
L29Ah has quit [Ping timeout: 264 seconds]
ur5us has quit [Ping timeout: 252 seconds]
castaway has joined #openscad
<Scopeuk>
I guess we could record the git revision at when we dropped formal support for specific ubuntu versions somewhere
use-value has joined #openscad
califax_ has joined #openscad
califax has quit [Remote host closed the connection]
califax_ is now known as califax
use-value has quit [Quit: use-value]
snaked has quit [Quit: Leaving]
<InPhase>
Scopeuk: It's probably more often that we just drop the effort to setup the build system for it. The code would usually still work if someone wanted to go through the effort.
L29Ah has joined #openscad
<Scopeuk>
InPhase I probably expressed it badly, marking up a "last known good" version so if it does break someone has a point to start digging
<teepee>
looks like Ubuntu 18.04 can stay for a bit longer
<teepee>
we don't seem to use anything from CGAL that actually needs 1.66, at least talking compile time
Lagopus has quit [Ping timeout: 260 seconds]
<teepee>
othx: tell kintel Ubuntu 18.04 builds on OBS look ok now, just waiting for the package mirrors to catch up so github sees the new package with lowered boost dependency
<othx>
teepee: I'll pass that on when kintel is around.
Lagopus has joined #openscad
<peepsalot>
InPhase: you are intimately familiar with rands right? is there technically a non-zero chance of hitting the upper bound exactly?
<peepsalot>
isn't it computed using 32bit values, so odds are 1:2^32?
<peepsalot>
or am I making some wrong assumptions there
<peepsalot>
gotta run, be back in about 4.5hrs
Shivam74 has joined #openscad
Shivam74 has quit [Client Quit]
SamantazFox has joined #openscad
Lagopus has quit [Read error: Connection reset by peer]
Lagopus has joined #openscad
Lagopus has quit [Read error: Connection reset by peer]
J2332 has quit [Quit: Client closed]
<InPhase>
peepsalot: std::uniform_real_distribution will internally generate two 32-bit values to get 64-bits so that it can make a properly random 53-bit double within the designated range. However it does this in range [a,b), so while there is a 1/2^53 chance of hitting a, there is a 0 chance of hitting b.
teepee has quit [Remote host closed the connection]
<InPhase>
peepsalot: Hence, rands for 0 to 1 will never produce 1.
<InPhase>
And, probably the documentation should actually say that.
teepee has joined #openscad
ur5us has joined #openscad
kintel has joined #openscad
J23 has joined #openscad
mlaga97 has joined #openscad
Lagopus has joined #openscad
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]