On Tue, 2003-07-15 at 23:36, Not Zed wrote: > Easiest way would be to build evolution yourself and disable any pilot > stuff. I think most packages you can get would have this stuff > built-in/part of the package dependencies and thus it can't be removed.
Define "easiest" :-> Do you know of a way to satisfy libpisock* with /usr/local/lib w/o compiling source (and not linking from /usr/lib)? Is there some 'trick' I can use to tell Evo to use my compiled libs instead (if revs are compatible)? Do you know how I can remove the tasks/appts/addrs that ended up in Summary after a test sync (man I wish I hadn't done that)? I do not want to use Evo for syncing. I already deleted ~/.gnome_pilot/ but the tasks/appts/addrs are still all over Summary (included alarm'd appts popping up and my Contacts overflowing with phone numbers I don't want in there!). There are a ton so I hope the answer isn't doing a caveman "del one at a time". I see there's Calendar and Contacts (addr*db) dirs with pilot* files that I could possibly delete, but like I said, before I make a huge mess I want to see if there's a correct way to undo this... Mike > On Tue, 2003-07-15 at 10:17, mail_acct wrote: > > Hi - > > > > Before I royally screw something up, how do I remove the Palm > > tasks/appts from summary page (and anywhere else in Evo)? > > > > If I remove gnome-pilot, pilot and evo-pilot, is Evo going to insist > > they be reinstalled next time I upgrade Evo? I compile pilot myself and > > the libs are in /usr/local/lib - will that satisfy Evo? > > > > Mike -- [EMAIL PROTECTED] _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
