[Thread Prev][Thread Next][Thread Index]
Re: is pilotmgr still being worked on?
I never tried pilot-manager under perl 5.003. I can't think of a good
reason to use 5.003. You say you have a tool that requires it; can I
ask what it is?
I'm stretching my memory for some of this, but here goes:
I started on a Debian 2.0 system. I was using the perl 5.004 and
perl-tk that are packaged with Debian 2.0. First, I built pilot-link
0.9, and installed the perl package. This gives me PDA::Pilot support
in my perl libraries.
Then I installed the basic PilotManager package from
http://www.moshpit.org/pilotmgr/binaries/. To do this, I got
latest.dev.tar.gz and untar'd it into ~/bin.
That's all I did. It works.
I also built my own perl 5.005 (from CPAN) in /usr/local; I installed
perl-tk using the -MCPAN tool, built pilot-link 0.9 & the perl tools
against it, and ran my already-installed PilotManager by chaning
/usr/bin/perl to /usr/local/bin/perl. Once again, it worked.
I recently upgraded to the pre2.1 Debian system. The current package
tree for 2.1 includes pilot-manager 1.106 and a fairly recent
pilot-link, a recent xcopilot, prc, and a full gcc development system
all pre-packaged. Look in dists/frozen/main/binary-i386/otherosfs for
pilot-manager. Be aware that the Debian people are big on modularity,
so the pilot-link perl support is a separate package from the base
pilot-link package.
If I were going to attempt to get this working on your system, the
first thing I'd do is get perl-tk working against your current perl. I
wouldn't trust the packaged TK stuff on www.moshpit.org for linux; for
one, I'd want my perl-tk libraries in sync with the tk that wish is
linked to.
As far as I'm concerned, the package page on the website is too
confusing. If it were up to me, I'd remove the tk and small stuff
entirely, and just indicate that the base package required
pilot-link+perl tools+perl-tk.
- Jim
Tim writes:
> > 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 *
> ***********************************************************
------------------------------------------------------------------------
***********************************************************
* This is a public mailing list! *
* Please do not publish Sun proprietary information here! *
* - - - - - - - - - - - - - - *
* http://www.moshpit.org/pilotmgr *
***********************************************************