[Thread Prev][Thread Next][Thread Index]
Re: Newest pilot manager problems ...
On Sat, Jan 10, 1998 at 09:35:12PM -0800, Alan Harder wrote:
>
> >From Marco:
> > I guess he put up the package after running PilotMgr.pm for the first time, in
> > which Setup finds the perl path and so now the updated PilotMgr.pm is in the
> > distribution.
>
> Yep, that's what I get for running PilotMgr right out of the development
> workspace :)
>
> I've fixed the file.. (the good thing about a friday release is hopefully
> not too many people got the file yet)
:)
> >From Seth:
> > Also, Alan, can we make the SyncCM stuff optional? I get a bunch
> > of harmless and ugly error messages everytime I load up PilotManager
> > because of my lack of having the necessary libraries. The ability to
> > remove conduits (regardless of whether or not they are loaded) would be
> > nice ...
>
> Simply rename the file to not end in ".pm".. then PilotManager won't look
> at it..
Yeah, I know that, and I've done, but that still is a hack (IMHO).
It would be nice if it isn't able to load a conduit, it wouldn't try
everytime, give you the option or not loading it every time or something
along those lines. I don't want to get that error every bloody time I
load ...
Also, what about "certifying" it for perl5.004_04?
-Seth
--
"It is by will alone I set my mind in motion"