irclog2html for #brlcad on 20100202

00:19.40starseekernot for later - issue with libtool and Tcl Stubs on Windows... http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/74cb58c3cdb7d252/cffcd1363cc2f684?lnk=gst&q=autotools#cffcd1363cc2f684
00:19.45starseekerer note
00:30.41*** join/#brlcad Tecan (~fsadf@unaffiliated/unit41)
01:31.01*** join/#brlcad ibot (ibot@rikers.org)
01:31.01*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
01:42.45*** join/#brlcad ibot (ibot@rikers.org)
01:42.46*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
01:50.43*** join/#brlcad ibot (ibot@rikers.org)
01:50.43*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
01:59.57*** join/#brlcad ibot (ibot@rikers.org)
01:59.58*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
02:09.27*** join/#brlcad ibot (ibot@rikers.org)
02:09.27*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
02:14.47*** join/#brlcad ibot (ibot@rikers.org)
02:14.48*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
03:09.04*** join/#brlcad Nohla (~jesica@201.255.242.124)
03:26.16*** join/#brlcad PrezKennedy (Matthew@whitecalf.net)
03:30.02*** join/#brlcad R0b0t1 (~Enigma@unaffiliated/r0b0t1)
04:06.35*** join/#brlcad Ralith (~ralith@69.90.48.97)
06:42.38*** join/#brlcad ``Erik (~erik@c-69-140-109-104.hsd1.md.comcast.net)
08:03.32*** join/#brlcad d_rossberg (~rossberg@BZ.BZFLAG.BZ)
08:30.46*** join/#brlcad Stattrav (~Stattrav@202.3.77.161)
09:51.07*** join/#brlcad Tecan (~fsadf@unaffiliated/unit41)
11:34.16Tecanthere be dragons
11:40.11``ErikO.o
11:40.36alex_joniat least not here :)
12:25.38Stattravand there be dragon hunters
13:13.18brlcadthey are tasty with some BBQ sauce
13:15.02CIA-43BRL-CAD: 03brlcad * r37520 10/brlcad/trunk/misc/win32-msvc8/Makefile.am: add the missing libanalyze to the dist
13:18.09CIA-43BRL-CAD: 03brlcad * r37521 10/brlcad/trunk/src/other/tkhtml3/Makefile.am: add a couple files missing from the dist
13:18.47Tecanhttp://www.youtube.com/watch?v=qswm7lHp7oY  << one tin soldier
14:14.21``Erikbbq sauce for dragon hunters? interesting
14:17.41*** join/#brlcad SWPadnos (~Me@emc/developer/SWPadnos)
15:34.28*** join/#brlcad indianlarry (~indianlar@BZ.BZFLAG.BZ)
15:35.24CIA-43BRL-CAD: 03brlcad * r37522 10/brlcad/trunk/src/other/tkhtml3/Makefile.am: heh, backslash happy
15:52.57*** join/#brlcad poolio (~poolio@BZ.BZFLAG.BZ)
15:53.10poolio``Erik: I'm learning about marching squares in class :)
17:24.33Stattravpoolio: which class in which university ? my prof barely touched it just mentioned it arbitrarily once
17:46.26CIA-43BRL-CAD: 03bob1961 * r37523 10/brlcad/trunk/include/opennurbs_ext.h: Quell some warnings when compiling 64-bit Windows.
17:47.30CIA-43BRL-CAD: 03bob1961 * r37524 10/brlcad/trunk/src/librt/ (38 files in 25 dirs): Quell some warnings when compiling 64-bit Windows.
18:14.13CIA-43BRL-CAD: 03starseeker * r37525 10/brlcad/branches/dmtogl/src/other/ (11 files in 5 dirs): Put back the ZLIB stuff in tcl/tk, but don't add it to the build system - need a way to pass in an external dir with the objects from the looks of it, based on manual tweaking of the gcc command used for tcl...
18:52.30*** join/#brlcad mafm (~mafm@195.Red-83-37-177.dynamicIP.rima-tde.net)
19:53.02*** join/#brlcad alex_joni (~alex_joni@emc/board-of-directors/alexjoni)
19:56.00*** join/#brlcad alex_joni (~alex_joni@emc/board-of-directors/alexjoni)
20:08.50CIA-43BRL-CAD: 03bob1961 * r37526 10/brlcad/trunk/src/librt/primitives/ (19 files in 19 dirs): The cast to long is now part of the bu_offsetof definition.
20:09.30CIA-43BRL-CAD: 03bob1961 * r37527 10/brlcad/trunk/include/bu.h: The cast to long is now part of the bu_offsetof definition.
20:44.08mafmhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=289632
20:44.17mafmit seems tough to get brl-cad in Debian!
20:48.38brlcadhey mafm .. ltns!
20:49.32brlcadthere are lots of things wrong with that RFP.
20:50.18mafmI'm a busy man, running all of my oil camp pumps and flying around with my bugatti veyron and stuff
20:50.20brlcadtitle should probably be "BRL-CAD", not BrlCAD or brlcad and not with the description in the title (unless there is no separate description section)
20:50.35brlcadmm.. that's a big car
20:50.39brlcada big HEAVY car
20:51.09mafm:D
20:51.46brlcadthere is absolutely no detail from "eugen" on his bad code quality assertion
20:52.17mafmyep, but after gsocing I'm very well paid... I can buy a veyron every month :PPPPP
20:52.56mafmthe thing is, did you provide debian packages with some release?
20:53.18mafmmaybe it's easy to provide a DD with it, and if it's a proper package, could upload it
20:53.50mafmwith the added benefit that it would probably drop on ubuntu repos too, I think
20:54.36mafmthe title is not important anyway, it's just some user asking to get it packaged
20:54.46mafmnot the proper description that it would have
20:57.57brlcadwe don't provide any distro-specific releases, that's up to a release maintainer for that platform subset
20:58.13brlcadwe have enough to do managing source releases and major OS binaries
20:59.16brlcad"Linux (with a particular GLIB)" is where that line is drawn, binaries that'll run on any Linux of a given runtime
20:59.39brlcadthere needs to be a debian dev to sort out the issues integrating with apt
20:59.46brlcadno diff than with portage, fink, ports, etc
21:00.20brlcadnow if someone sorted out the build logic and make it a simple "make && make deb" which resulted in a .deb, that's something we could probably support
21:00.23brlcadthere'
21:00.38brlcadthere's hooks in the build system already for someone to fill in the logic, but to date nobody has stepped up
21:03.31CIA-43BRL-CAD: 03bob1961 * r37528 10/brlcad/trunk/src/libbu/ (11 files): Quell some warnings when compiling 64-bit Windows.
21:12.23*** join/#brlcad mafm_ (~mafm@99.Red-83-45-252.dynamicIP.rima-tde.net)
21:12.43CIA-43BRL-CAD: 03bob1961 * r37529 10/brlcad/trunk/src/libbn/sphmap.c: Quell some warnings when compiling 64-bit Windows.
21:13.04mafm_I thought by reading the RFP that you already provided that in the past
21:16.43*** join/#brlcad R0b0t1 (~Enigma@unaffiliated/r0b0t1)
21:17.05mafm_when brl-cad installs, all of include files, libs used by binaries and a lot of binaries themselves are installed, right?
21:17.20mafm_is there any doc and data too, I guess?
21:18.39brlcadthere has been one .deb posted, which was user-provided
21:19.00brlcadyes, it's the whole shebang, however it was configured
21:19.27brlcadif you compile it not use any provided libs, you have to have them all system-installed beforehand
21:20.01brlcadif you compile it to use all provided libs, it will be a completely stand-alone install with no additional dependencies (other than the C runtime) which is usually how binaries are built
21:20.23brlcadif you compile with auto-detection enabled, it'll run on systems matching the one you compiled
21:22.07mafm_but I mean, regarding libs, that it also installs internal libs dynamically shared, like librt or libu, right?
21:22.46brlcadyes, all of the brl-cad libs, a few hundred binaries, some resource data, documentation files
21:22.54brlcadstandard fare
21:22.57mafm_that's how it should be done in debian anyway, and not use any statically compiled stuff if possible
21:23.27brlcadyes, on debian, it should be a ./configure --disable-all build and have a deb package file that describes all of the dependencies
21:23.36brlcadnot rocket science, not even hard at all
21:23.46brlcadjust nobody knowledgeable has tried
21:23.58mafm_the problem is that you have to separate all of them into packages
21:24.11mafm_it's similar with OpenSceneGraph that I updated recently
21:24.27mafm_(but I didn't have to create from scratch)
21:24.28brlcadonly a few hobbiest users that have *wanted* a deb, never made a deb before in their life, some that haven't even really compiled before
21:25.08brlcadnone of the issues I've heard mentioned have been about separation
21:25.15brlcadit's been about competence
21:25.24mafm_so there's libopenthreads (bin and dev), libosg (bin and dev) with many plugins, openscenegraph-doc, openscenegraph-data, openscenegraph-bin with samples and converter tools...
21:25.27brlcadthey didn't really seem to know what they were doing
21:26.02brlcadisn't that up to the project to decide how to chop things up -- don't recall ever having seen anything about separation being a requirement
21:26.19brlcadand individual libs that are projects by themselves are already not an issue
21:26.32mafm_it's part of the debian policy to separate it that way
21:26.43mafm_AFAIK
21:26.53mafm_of course, BRL-CAD as a project or anybody, can provide a .deb with everything
21:26.58brlcadit's more complex projects (like X11 or SVN or OpenSSH) that have multiple binaries and libraries
21:27.14brlcadsvn isn't just "svn"
21:27.18brlcadthey have about a dozen libraries
21:27.25brlcadthey're certainly not separated last I saw
21:27.36mafm_hmm
21:27.41brlcadsimilar with the X11 core (not even counting Xt, Xi, etc)
21:28.11mafm_there's libsvn, subversion, and subversion-tools
21:28.14brlcadit's just a matter of size -- there are only so many "big" projects with code bases > 100k
21:28.40mafm_and x.org is completely modular now in debian
21:28.43brlcadright, as I would expect, that's a reasonable breakout -- but svn has more libs than that
21:29.04mafm_hmm
21:29.19brlcadthe corrollary would be making a package for our libbrlcad
21:29.26brlcad(which needs to be renamed, ugh)
21:29.51mafm_well, you don't have to provide a separate package for every library and binary
21:30.10brlcadI wouldn't even think to do that :)
21:30.14mafm_just a sensible separation, specially non-binary data
21:30.26mafm_by now Debian has around 11 architectures and several kernels (hurd and freebsd)
21:30.43brlcadthat doesn't exactly solve the current problem
21:31.25brlcadsure a good thing to do, but the problem has been someone simply competent in making a .deb knowing how to set things up and deal with various configuration issues
21:31.32mafm_the mirrors are very very huge, and they don't want to repeat data needlessly (non-binary packages are shared in a common pool for all architectures)
21:32.07brlcadour non-binary data is very miniscule at the moment
21:32.16mafm_hmm, I might give it a try, but I don't promise anything
21:32.18brlcaddocs are growing, but still tiny in comparison
21:32.24mafm_just updating OSG was a bit PITA :D
21:32.44brlcadat the point we have all docs in docbook format and are generating pdf files, then docs will be huge
21:32.53brlcadbut that's at least a year out
21:33.12mafm_I agree that .configure && make is not rocket science, but somehow creating Debian packages is very cumbersome
21:36.15brlcadthis is a great example:  http://bugs.gentoo.org/show_bug.cgi?id=77197
21:36.22brlcadthe gentoo ebuild is in a similar boat
21:36.53brlcadit has been hit up by many many people over the years, and just today was looked at by someone knowledgable that whipped up an ebuild in very short order
21:37.03brlcada completely new ebuild I might add
21:37.10alex_joniif you do make install then building a deb is not that hard
21:37.39alex_jonibuilding a deb that gets accepted in the debian repos however is a bit trickier..
21:37.52mafm_biggest problem might be name clashes or something, librt or libu are not terribly "unique-like" :D
21:38.38brlcadwe've sorted out most all of the name clashes I'm aware of, and made many insignificant by installing libs into a subdir
21:40.44alex_jonicomplying with the LFHS is another topic
21:40.57mafm_how so? like /usr/lib/brlcad/libu.so?
21:41.04brlcadyeah, like that
21:41.12mafm_debian adheres to FSH too :D
21:41.22alex_jonihttp://www.debian.org/doc/debian-policy/ch-opersys.html
21:41.24brlcadall just a configure flags
21:41.47alex_jonibrlcad: then it's the point of debian/rules to just invoke the proper configure invocation
21:41.55alex_jonisurely not a hard thing to do
21:42.02brlcadexactly my point
21:42.41brlcadnothing hard, just few knowledgeable have tried
21:42.58alex_joniwell, it depends what you want to do with the packages
21:43.04alex_jonibuild a repo and maintain it?
21:43.14mafm_are there any dependencies? kind of ogre in g3d?
21:43.25alex_jonipush it to debian, and be done with it.. ubuntu maybe? etc
21:43.47alex_jonimafm_: what do you mean?
21:43.49brlcadalex_joni: I still believe that's not time we should waste
21:44.07brlcadby we, I mean an active developer capable of working on the code
21:44.12alex_jonibrlcad: guess that's why there are no packages out there ;)
21:44.14brlcadit should be done by a user for that OS/distro
21:44.19alex_joniright
21:44.25alex_jonithat's your call..
21:44.49brlcadif there's nobody for that environment (yet), so be it .. in the meantime, we have PLENTY to work on (e.g. make things easier to use)
21:45.11alex_joniwe did it for our software, as we planned to use debs as the primary way of distributing the software
21:45.28alex_joniand are still doing it 4? years later ;)
21:45.39brlcadthat's 1-2 days for debian, 1-2 days for gentoo, .. fedora, fink, redhat rpms, etc...
21:45.47brlcadit's just not a productive use of time
21:46.20alex_joniyou're certainly right about one thing, it's work that can be done by anyone with packaging skills
21:46.24brlcadthere are a hundred "1-2 day" tasks that are perfectly justified in exactly the same way that can be performed by a non-developer
21:46.38alex_jonino need to know BRLCAD internals for that
21:47.31brlcadif there isn't someone willing or capable of doing it yet, that's fine -- it's not something that needs to be forced, it'll happen when we've made things "easy enough" for it to happen
21:47.53brlcadthings are WAY better than they were 4 years ago
21:48.10alex_joniit'll bring more exposure (users).. but then again, it's up to you to decide if that's really needed ;)
21:48.27alex_jonior helpfull
21:48.41brlcadright
21:48.50brlcadI don't think it's helpful if we have to push to make it happen
21:49.22alex_jonior if you get a ton of users in here asking how to right click in mged
21:50.24brlcadright
21:52.00mafm_alex_joni: src/other sometimes contains software that brl-cad need
21:53.05mafm_like Ogre that it's needed for g3d
21:53.31mafm_obviously you cannot put that into debian package
21:55.39brlcador "simple" feature requests like "how can I get a shaded view of geometry"
21:55.50alex_joniright.. but you can make the brlcad package depend on the needed package
22:04.13brlcadsrc/other should contain ALL of our dependencies with the exception of the C runtime, curses (optional), X11 (optional), and OpenGL (optional)
22:04.53brlcadthere are a couple of src/other items that are basically unmaintained or niche codes
22:05.06brlcadworking out taking over maintainership of them for the fedora folks
22:10.14mafm_all of those would have to be in debian or packaged separately
22:14.47brlcador treated as private libs
22:14.54brlcadwhich is what most projects do
22:15.26brlcadwe just make it explicitly clear that they're not code we wrote for maintainability and licensing purposes
22:15.42brlcadmost projects would throw that in with the rest of the sources, link against it static and be done
22:15.50brlcadno problems because it really is that niche a code
22:16.55brlcadnobody would even know we use the TNT code if we didn't tell them .. nothing gets compiled, just a bunch of template headers
22:17.07starseekerthe utahrle stuff and step we could probably move into src as our own libraries and nobody would blink - I don't know if I've ever heard of a system having those externally installed...
22:18.05CIA-43BRL-CAD: 03bob1961 * r37530 10/brlcad/trunk/src/libdm/ (axes.c dm-Null.c dm-wgl.c dm_obj.c): Quell a few warnings when compiling 64-bit Windows.
22:18.17brlcadright, they're another good example
22:18.29brlcadthe reason we can even take them over is because they're not maintained
22:19.22brlcadI used to see utahrle installed in places, but not in probably 5-10 years
22:20.37brlcadanyone care to place a bet on whether bob injects a bug with all of the 64-bit quelling? :)
22:21.53CIA-43BRL-CAD: 03bob1961 * r37531 10/brlcad/trunk/src/libfb/if_remote.c: Quell a few warnings when compiling 64-bit Windows.
22:23.20starseekerheh - not a dime
22:25.35starseekerindianlarry: how did you compile step-g so that everything got included?  
22:37.09*** join/#brlcad PrezKennedy (Matthew@whitecalf.net)
22:52.10mafm_I'm sure it's forbidden to include tcl version x.x for example, because brl-cad requires it and in thebian there's version x.z
22:52.31mafm_which is one of the issues raised in the Request For Package item
23:33.47``Erik"that show quit being funny after kristie alley ate shelly long" yow O.o :D
23:34.16brlcadmafm_: tcl is a managed external lib, we wouldn't even install it
23:34.49brlcadthat issue in the RFP is bogus iirc

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with infobot logs, split per channel, etc.