[Thread Prev][Thread Next][Thread Index]
Re: is pilotmgr still being worked on?
- To: jim@xxxxxxxxxx
- Subject: Re: is pilotmgr still being worked on?
- From: "Tim" <tim@xxxxxxxxxxxx>
- Date: Wed, 13 Jan 1999 10:57:00 -0500
- Cc: Dan Simoes <dans@xxxxxxx>, steveo@xxxxxxxxxxxxx, pilotmgr@xxxxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <13980.47409.915741.327313@osiris.kosmic.org>
- Organization: LMR Group / GTL inc.
- Priority: normal
- References: <199901131433.JAA32108@gate.lmrgroup.com>
- Reply-to: tim@xxxxxxxxxxxx
- Sender: owner-pilotmgr@moshpit
> I'm running Linux, and I have none of the problems either of you
> mention. I run PilotManager at least twice a day.
>
> The "official" distributions of PilotManager *did* require some
> tweaking to get them working on my machine. It helps tremendously to
> install the /perl subdirectory of the pilot-link utilities before
> trying to build PilotManager.
As far as I know, nobody has Pilot manager for Linux working ? If
you did get one working I would be interested in where you got the
distribution and what "tweeking" you needed to get it to work. I
maintain at least one of each of the Linux versions (readhat,
debian,slackware etc..) so I would be interested in which version of
Linux you did it on.
>
> I disagree that maintaining perl and tk are problematic. Try
> "perl -MCPAN -e shell", which has worked for me for a long time.
What I meant was that I have another application that uses Perl and it needs
release 5.003 and now I suspected the Pilotmanager needed 5.004
(because of the distribution site not having the proper Tk in the
5.003 Tk file, thay have 5.002 in that file I think). Perl lets a
programmer write in one language (like many languages have tried
to do) but Perl application programs need specific releases of Perl.
Thats the pain. This is shown by the fact that PilotManager has at
least three or four versions to try to suit the releases of Perl people
are using.
> I have TWO working copies of PilotManager on my linx i386 >
system; one
> is my original hand-installed copy from the distribution, the other is
> from now-frozen Debian 2.1 packages. On the other hand, I've *never*
> gotten PilotManager to work on my Sparc/Linux system, which runs
> RedHat 5.2. I've used Linux since 0.99 kernels. I've used slackware, redhat,
> debian, and suse distributions. In general, RPM-based distributions have
> proven difficult to maintain, and I've had very little success with
> locally built tools on these systems. Over against this is my
> experience with Debian, which just plain works for me.
I also maintain multipule distributions. It seems to me that every
distribution wants its "OWN" maintance tool ergo some problems
for the future of Linux. I sway towards slackware. Everything works
there and I can even port stuff from RPM or deb to it if needed. So I
would welcome any info on a suspected working Pilot Manager for
perl 5.003.
Thanks for all your help guys !
,, Tim
***********************************************
Tim Ertl @ LMR Group tim@xxxxxxxxxxxx
phone 413-442-9000 x6211 fax 413-442-9000
SGI bought Cray ? Should have been the other way !
***********************************************
Radio: KE3HT
Also on APRS: 145.79
internet ke3ht@xxxxxxxx -or- ke3ht@xxxxxxxxxxxx
***********************************************
------------------------------------------------------------------------
***********************************************************
* This is a public mailing list! *
* Please do not publish Sun proprietary information here! *
* - - - - - - - - - - - - - - *
* http://www.moshpit.org/pilotmgr *
***********************************************************