[08:15] <duflu> tsdgeos: Is the shell's text rendering ubuntu-ui-toolkit or regular Qt stuff?
[08:17] <tsdgeos> duflu: i wouldn't say the ubuntu-ui-toolkit has any own text rendering
[08:17] <tsdgeos> i hope so at least :D
[08:18] <duflu> tsdgeos: Lemme rephrase that: Who calls into FreeType?
[08:18] <tsdgeos> Qt if anyone
[08:18] <tsdgeos> i have the word harbuff inside my mind
[08:18] <tsdgeos> not sure if that replaces freetype or not
[08:19] <duflu> tsdgeos: HarfBuzz?
[08:20] <tsdgeos> duflu: that
[08:21] <duflu> Yay, another fork I didn't know existed
[08:22] <tsdgeos> it's quite old
[08:23] <tsdgeos> afaik gtk is using this too
[08:24] <duflu> Yeah apparently FreeType links to it
[08:28] <tsdgeos> so as said, it may not be "the same thing" as freetype
[08:31] <duflu> tsdgeos: That's OK. My question was who calls the relevant libraries. Not what the libraries are
[14:03] <Saviq> alf_, so I've been thinking, if we manage to get jenkins-job-builder and/or DSL working, no point in having the scripts in the repo separately, the might as well be baked into the jobs if the job definitions are stored in bzr
[14:04] <Saviq> alf_, so I'm gonna look into that instead of putting them into bzr
[14:05] <alf_> Saviq: ok, although one thing that concerns me is that jobs will need to have different defaults depending on project, how will we deal with this?
[14:10] <Saviq> alf_, I'm sure there are ways
[14:10] <Saviq> alf_, like a config file or global env vars
[14:12] <Saviq> alf_, it seems like jenkins-job-builder doesn't even need to run on the jenkins nodes necessarily, as all it does is upload xml via the API
[14:13] <Saviq> alf_, so assuming we can make stuff smart, you'll just set up some config vars and let JJB do its thing
[16:04] <QUESTION> ?
[16:05] <ogra_> 42
[16:05] <QUESTION> what's my nickname?