00:09 <ehawkvu> Merry Christmas!

06:40 <sad_plan> hi

06:40 <sad_plan> wym how sewn

07:40 <abhi> hi

07:48 <sad_plan> hi abhi

08:17 <sewn> sad_plan: how how about

08:20 <sad_plan> how about you? how has the holidays been for you so far

08:20 <sad_plan> thats what I asked

08:23 <sewn> we don't have holidays at this time

08:36 <sad_plan> right

16:54 <Guest1196> does anybody here have ANY patch that removes icu dependency from ANY software?

17:16 <sewn> from what

17:16 <sewn> you gotta be specific

17:16 <sewn> you cant patch icu out of a non-icu software

18:25 <abhi> hi

18:25 <sewn> hi abhi

21:21 <riteo> Hi KISS folks, I've got an interesting question. What's the current state of the art in regards to language bootstrapping? That seems to be the biggest issue we're having in regards to building complex software (e.g. JDK), other than the issue of properly caching every build dependency

21:23 <riteo> I've been wondering if we could perhaps add be a special bootstrap dependency type (like `make`), that can optionally "pull in" something like a bootstrap payload if needed

21:24 <riteo> I see that we already have a package named `go-bootstrap`, but we use that as a make dependency every time the `go` package is built, indepenently of whether we need it or not. Is there a specific reason for that?

21:25 <riteo> Uh no wait I think I'm not grasping the full problem space.

21:27 <riteo> _why_ do we have the go-bootstrap package in the first place? Is it to avoid building it many times? I'd like to know further context to know how's the situation, becuase it might be me misunderstanding it as a problem, sorry.

21:30 <riteo> I'd seriously like to package the JDK because I actually need it for some stuff (yeah, I know that it's bloated, I can't do much regarding that) but I wonder how hard it would be to bootstrap to a modern version, supposing that the dependency fetching problem is solved (it isn't)