On Wednesday, Mar 26, 2003, at 22:30 Europe/London, S Woodside wrote:
Anyway, I guess that 1.6.1 doesn't really work on debian 2.2, is the
upshot.
I wouldn't go that far. I suspect it can be made to work.
Sure, with hours of hacking as I don't have root so I'm going to start
installing
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).
simon
On Wednesday,
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
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
On Tue, 25 Mar 2003, S Woodside wrote:
Well i think I finally figured out why my buddy's having trouble
installing 1.6.1 on his box ... turns out he's running debian 2.2 which
has a known problem detecting iconv. The workaround apparently is
either something very complex involving testing
