On Wed, Mar 26, 2003 at 06:53:38PM -0500, S Woodside wrote: > To add to this, sorry for the spam but I think this is > relevant/important. A lot of the discussion on this list seems to > assume that those involved consider modifying the AxKit code itself to > be a reasonable solution ... to me that's just not an option. Sure, I > could probably do it (after a week of learning more perl) but I'm not > interested and I'd rather spend my time learning XSLT etc. So > suggestions of the nature of "it could be hacked to make that work" are > somewhat unhelpful. > > simon > > On Wednesday, March 26, 2003, at 06:49 PM, S Woodside wrote: > > >Well, part of my frustration is generally that the axkit > >user/developer base is small. Smaller than it should be IMHO (I can't > >comment on why that might be true for the developer base but there > >doesn't seem to be as much user understanding of what a userful tool > >it is).
Go ahead and post the output (or post the output somewhere) of Makefile.PL DEBUG=1 might as well make all the info available and somebody might catch the problem. how you present the problem to people makes a big difference. you need to motivate, encourage and get peoples brains turned to thinking about your problem. w/ the output you just might spark someone's interest .... i think you'll get a better response is you present things as an interesting challange to people around here. you'll loose everytime you bitch about poor tech support. you should also keep it quiet that your not willing to help yourself ... Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
