[Thread Prev][Thread Next][Thread Index]

Re: Problem encountered with SyncCM



> Has anyone else figured out what needs to change in Pilotmanager to get
> this to work?  Do I need to _delete_ the binary version of lib/* for
> perl Tk to get this to work?

Yes, absolutely.  perl will look in the pilotmgr/lib section before the
default perl lib directories, so if you have a Tk binary in there for some
other version of perl it won't work.

When building a new installation you should install only the Basic package.

> What I worry about though is whether there were pilotmgr related 
> modifications or modules in those files.

No, the binary packages on the web page contain nothing pilotmgr specific.
They are only there to save users from having to build those packages
themselves.

> Finally, where does one install the various .pm and .pl files in the contrib
> directory?  Is there a particular location?  Is there something I need
> to do so that pilotmgr recognizes the various new 'conduits'?

PilotManager looks for conduits in two places:
1. the pilotmgr directory
2. your ~/.pilotmgr directory

Note that if you share a pilotmgr installation among many users then #1 is
shared space, and #2 is per user space.
To use a conduit from the contrib section copy it to one of the above places.
Then you need to either restart pilotmgr or choose "Load New Conduits" from
the menu so pilotmgr will see it.

	- Alan
------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************


SourceForge.net Logo