Back
[00:41:18] <skunkworks> jmkasunich: Looks really good. The tramming of the machine seemed to help also :)
[00:43:38] <A-L-P-H-A> skunkworks: what RPM are you going at? and what style cutter?
[00:45:20] <skunkworks> thinkandtinker bits - the ones that cradek uses.. And a rotozip
[00:45:43] <A-L-P-H-A> oh... so somewhere between 10K and 35K rpm.
[00:46:27] <A-L-P-H-A> I wonder is there a way to go a closed loop system with a rotozip/dremel... to maintain constant RPMs while milling/drilling.
[00:57:03] <jmkasunich> skunkworks: glad to hear that
[00:57:05] <jmkasunich> pics?
[01:12:25] <A-L-P-H-A> woohoo! picture time!
[05:49:47] <A-L-P-H-A> denied picture time! :(
[09:16:30] <alex_joni> https://wiki.ubuntu.com/APTonCD <- interesting
[11:47:35] <jepler> looks interesting. is it written yet?
[11:53:26] <alex_joni> http://aptoncd.sourceforge.net/
[11:54:11] <alex_joni> under development still
[13:48:26] <Guest575> Guest575 is now known as Skunkworks_1
[15:20:48] <jepler> Unpacking replacement emc2 ...
[15:20:48] <jepler> dpkg-deb: unexpected end of file in between members in emc2_2.1.0pre_i386.deb
[15:20:48] <jepler> Segmentation fault
[15:20:50] <jepler> outh
[15:20:51] <jepler> ouch
[15:21:27] <alex_joni> ouch
[15:21:57] <alex_joni> eek
[15:22:05] <rayh_> yuck
[15:22:45] <cradek> jepler: be careful of the version number so we don't have to use 1:2.1.0 later
[15:23:04] <cradek> if you intend to distribute this pre package I mean
[15:25:03] <jepler> I suspect we'll have to use 1:2.1.0 anyway
[15:25:08] <jepler> it gave me this warning also when I tried to install:
[15:25:09] <jepler> dpkg - warning: downgrading emc2-dev from 1:2.0.3 to 0:2.1.0pre.
[15:26:48] <cradek> yep I bet you're right
[15:27:05] <cradek> if we intend for it to replace 2.0
[15:27:50] <cradek> I don't think we've decided how it will all work - we surely don't want to upgrade everyone to 2.1 automatically
[15:29:44] <alex_joni> cradek: maybe do it like python2.3 and python2.4
[15:29:50] <alex_joni> different packages & versions
[15:30:35] <cradek> yes maybe so, but what a mess
[15:30:42] <cradek> brb
[15:30:48] <jepler> right now I'm interested in getting the packages to build again
[15:31:10] <jepler> and, y'know, be usable
[15:48:19] <jepler> OK, what's the trick to making emc_module_helper setuid in the .deb?
[15:49:09] <jepler> HAL:5: ERROR: execv(${exec_prefix}/bin/emc_module_helper) failed
[15:49:10] <jepler> oh yuck
[15:49:40] <cradek> there's a trick, some flag to the thing that sets the permissions
[15:49:50] <cradek> look at the old one
[15:50:05] <jepler> dh_fixperms -X/emc_module_helper
[15:50:08] <jepler> I started with the old one
[15:50:21] <cradek> yeah that
[15:50:41] <cradek> does make install not set it correctly?
[15:51:20] <jepler> I'm not sure
[15:51:40] <jepler> I've been taking shortcuts, not running dpkg-buildpackage but invoking debian/rules
[15:51:51] <jepler> so maybe it's PEBKAC
[15:52:06] <cradek> ah
[15:52:29] <jepler> this problem where the config.h path has $s in it sucks
[15:53:20] <cradek> I don't know what that is
[15:54:55] <jepler> #define EMC2_BIN_DIR "${exec_prefix}/bin"
[15:55:30] <jepler> I arranged for all the paths to be in config.h rather than on the commandline
[15:56:44] <jepler> but apparently that doesn't work when it's not RIP
[16:04:31] <jepler> found the module_helper problem, it was being installed twice .. the first time with 4755, the second time with 755
[17:40:58] <rayh> I get an error message when I try to run classicladder in 6.06
[17:41:19] <cradek> cvs head?
[17:41:23] <rayh> unable to locate loadable module in module_path: "libindustrial.so"
[17:41:33] <rayh> 2.0.3
[17:41:39] <cradek> wtf
[17:41:52] <rayh> beats me.
[17:42:00] <rayh> Let me try it here with 5.10
[17:42:22] <cradek> it's a gtk theme
[17:42:57] <cradek> try installing gtk-engines-industrial and gtk2-engines-industrial
[17:43:47] <cradek> something about the themes must have become screwy on that system?
[17:43:47] <rayh> Ah what I'm seeing here about the same place in the run is something about modbus.
[17:44:08] <rayh> or change the theme.
[17:44:21] <cradek> yeah maybe going to the default theme will fix it
[17:44:28] <cradek> not sure what it's all about
[17:45:54] <rayh> Right. It does.
[17:46:05] <rayh> That is an interesting artifact.
[17:46:38] <cradek> I bet CL is built with gtk1 and the theme is installed for gtk2 only
[17:47:07] <rayh> Okay. That sounds like a reasonable explanation.
[17:47:21] <rayh> thanks
[17:47:27] <cradek> welcome
[17:48:56] <rayh> I'm seeing that we don't have the proper file in common to handle classicladder for the motenc config.
[17:49:11] <cradek> uh-oh
[17:49:34] <rayh> I'll add a clp file in that and revise the motenc_io.hal
[17:49:38] <cradek> if you check in a fix on the v2_0_branch it'll get fixed in 2.0.4
[17:49:57] <rayh> oh. okay.
[17:50:49] <rayh> do I have to check out the 2.0 branch to do that?
[17:51:14] <cradek> yes that's the best way
[17:52:42] <rayh> -rv2_0_3_branch ??
[17:52:52] <cradek> -rv2_0_branch
[17:53:16] <rayh> oh. Thanks
[19:26:08] <jepler> I'd forgotten about this added feature:
http://emergent.unpy.net/files/sandbox/copyconfig.png
[19:27:06] <Skunkworks_1> jepler: That feature would help a lot of linux newbies
[19:28:20] <jepler> What about documentation? Should I include the pdf documentation, the html documentation, or both? they're each about 5 megs, installed.
[19:28:35] <jepler> I could split it out into another package (emc2-doc)
[19:28:37] <cradek> sure would be nice
[19:28:46] <jepler> or emc2-doc-html and emc2-doc-pdf
[19:28:46] <jepler> even
[19:29:45] <cradek> I suppose it should be separate shouldn't it
[19:30:24] <SWPadnos> user docs should probably be included, integrator/developer docs should be in a separate package
[19:30:34] <SWPadnos> I'm not sure if they're separate at this point though
[19:32:14] <cradek> jepler: if you put the Copy Configuration? in, I have a suggestion about the grammar
[19:36:43] <jepler> cradek: it's in. please fix the grammars.
[19:37:26] <jepler> tcl/bin/pickconfig.tcl:320: set res [tk_dialog .d [msgcat::mc "Copy Configuration?"] ......
[19:37:48] <alex_joni> jepler: now that we're talking about pickconfig..
[19:37:59] <alex_joni> there would be another idea
[19:38:43] <jepler> what's that?
[19:38:43] <alex_joni> we have an .emcrc .. there are still users that complain that emc isn't starting by default with the chosen config
[19:38:59] <alex_joni> how about we have 2 menu entries (EMC-pick, EMC)
[19:39:35] <alex_joni> I first thought about a checkbox in the pickconfig, ([ ] Start this config by default)
[19:39:46] <alex_joni> but it's hard for newbies to revert then
[19:40:50] <cradek> I think having EMC-pick and EMC in the menu is otherworldly
[19:41:48] <cradek> ... that being said, I'm having trouble suggesting an alternative
[19:42:12] <cradek> I don't see any problem with "the user makes a launcher" like he would for any other program he wanted to start up with certain commandline options
[19:42:38] <cradek> jepler: argh, I started out to fix a simple thing, but I also added more words
[19:43:06] <SWPadnos> how about a button to "create an icon for this confiuguration" or some such?
[19:43:22] <SWPadnos> that should be about as easy as a sed + copy operation
[19:43:30] <SWPadnos> (key word: should)
[19:43:38] <cradek> that's unfortunately very specific to a particular desktop environment
[19:44:09] <SWPadnos> theoretically, a desktop icon (vs a menu item) should be the same for kde, gnome, or xfce
[19:44:25] <cradek> I didn't know that
[19:44:39] <SWPadnos> I think they all claim to support the freedesktop.org spec
[19:44:59] <SWPadnos> whether that's true or not, I don't know
[19:47:06] <jepler> I will add 'emc -l' to use the 'l'ast configuration file, from emcrc
[19:47:16] <jepler> it's up to you folks to do something clever and desktoppy
[19:51:08] <alex_joni> heh
[19:53:59] <jepler> hm that didn't work like I thought it should. I'll try to add "-l" later.
[20:44:22] <alex_joni> jepler: still around?
[20:44:35] <alex_joni> I was just reviewing the changes you made to emc2/debian
[20:44:46] <alex_joni> can you do the changes to control.in too?
[22:56:44] <jepler> alex_joni: I'll look at that later, but yes if that's the right way
[22:56:53] <jepler> if control is a generated file, it should be removed from cvs
