| 01:39.15 | *** join/#brlcad Twingy (~justin@pcp0011643033pcs.aberdn01.md.comcast.net) | |
| 05:21.00 | brlcad | he's in hiding |
| 05:22.13 | brlcad | so the guy working on the debian package is suggesting some organizational changes at least for that platform |
| 05:22.50 | brlcad | I'm inclined to allow an optional configuration option to specify those alternate paths |
| 05:23.16 | brlcad | e.g. to install libs into $prefix/lib/brlcad/ and headers into $prefix/include/brlcad/ |
| 05:26.38 | narnia | that would break the past de facto standard though. |
| 05:27.02 | brlcad | that's why I'm just inclined to make it allowed, not make it default |
| 05:27.27 | narnia | ah, understand |
| 05:27.51 | narnia | sounds like a good compromise. |
| 05:27.55 | brlcad | it's not unprecedented.. it's what X11 does and they parallel brl-cad complexities in many ways |
| 05:29.39 | narnia | true, but x11 is going through major pains at the moment. xfree86 is pretty much done with. freedesktop.org is becoming the de facto install. |
| 05:30.02 | brlcad | x11 has taken over xfree86 |
| 05:30.37 | brlcad | er, x.org to be more specific |
| 05:30.43 | narnia | yes. |
| 05:31.09 | narnia | that whole license fiasco. |
| 05:32.08 | brlcad | yeah |
| 05:32.21 | brlcad | that was a huge blunder on the xfree maintainer's part |
| 05:33.07 | brlcad | that's the risk of holding strong inflexible positions as a maintainer.. |
| 05:34.54 | narnia | david's ego got in the way. |
| 05:36.04 | brlcad | yep, and pride |
| 05:36.11 | narnia | definitely. |
| 05:39.48 | narnia | btw, who is jano? i have no idea who he is, but i find i like him. |
| 05:41.07 | brlcad | heh |
| 05:41.54 | brlcad | he's an old friend |
| 05:42.16 | brlcad | used to be a modeler, but not with brl-cad |
| 05:43.33 | brlcad | I usually end up meeting up with him at/after siggraph every year |
| 05:46.57 | narnia | i like his humor. |
| 05:47.31 | narnia | he did however leave me locked in the cage of doom. ;-) |
| 05:47.52 | brlcad | you're doomed! |
| 05:48.33 | narnia | oh no! |
| 05:49.10 | brlcad | heh, yes he's full of some sort of humor :) |
| 05:49.28 | brlcad | and he usually hangs out here to release stress and fool around ;) |
| 05:49.40 | narnia | good reasons. |
| 05:50.08 | narnia | did you ever see my msg from last night? |
| 05:50.17 | narnia | private msg. |
| 05:50.25 | brlcad | yes, I did |
| 05:50.30 | narnia | you were talking with EricWilhelm . |
| 05:50.59 | brlcad | indeed |
| 05:51.00 | narnia | i was trying to follow the conversation. |
| 05:54.26 | narnia | hang on need to put some medicine gradpa cat;s chin |
| 06:17.19 | brlcad | http://books.slashdot.org/article.pl?sid=05/03/02/1951204&tid=156&tid=108&tid=6&tid=7 |
| 07:19.48 | CIA-8 | BRL-CAD: 03brlcad * 10brlcad/configure.ac: duplicate strerror and check for strerror_r |
| 07:25.38 | CIA-8 | BRL-CAD: 03brlcad * 10brlcad/src/libpkg/pkg.c: potentially requires sys_errlist, so need optional extern declarations. |
| 07:46.53 | CIA-8 | BRL-CAD: 03brlcad * 10brlcad/src/libfb/if_disk.c: potentially need both sys/file.h and fcntl.h so separate them (solaris fix) |
| 08:03.11 | narnia | i thought sys_errlist was deprecated in favour of strerror()? |
| 10:11.29 | *** join/#brlcad Pimpinella (~frank@p50820E10.dip0.t-ipconnect.de) | |
| 13:43.17 | brlcad | it is |
| 13:43.35 | brlcad | but when strerror is not available, it falls back to errlist |
| 13:43.51 | brlcad | and this is such a system that did not have strerror |
| 16:25.24 | narnia | ah, understand. |
| 21:28.05 | narnia | brlcad, does brl-cad handle unicode (utf-8)? how well does brl-cad handle unicode (utf-8)? the reason i ask is that part11 and part24 both allow unicode. |
| 22:34.35 | brlcad | I'm actually not sure how well it'll stash/reload utf-8 from the geometry format or internal representations |
| 22:35.47 | brlcad | the actual converter support is in the domain of the converter's front in, so the only real issue is how utf-8 is handled internal to the .g format |
| 22:36.16 | brlcad | it shouldn't be too hard if it doesn't work quite right as the file format itself simply records a length and is followed by an array of bytes |
| 22:36.28 | brlcad | translation to utf-16 should be even possible |
| 22:37.11 | brlcad | little chance mged would handle it without modification, though as I'd bet it'll choke on utf-* |
| 23:00.29 | narnia | brlcad, okay thank you. |