From owner-freebsd-ports Sun May 13 12:29:46 2001 Delivered-To: freebsd-ports@freebsd.org Received: from h24-69-46-74.gv.shawcable.net (h24-69-46-74.gv.shawcable.net [24.69.46.74]) by hub.freebsd.org (Postfix) with ESMTP id 23CEF37B423 for ; Sun, 13 May 2001 12:29:43 -0700 (PDT) (envelope-from michael@tenzo.com) Received: from h24-69-46-74.gv.shawcable.net (localhost.gv.shawcable.net [127.0.0.1]) by h24-69-46-74.gv.shawcable.net (8.11.3/8.11.3) with SMTP id f4DJWBL02241; Sun, 13 May 2001 12:32:11 -0700 (PDT) (envelope-from michael@tenzo.com) Content-Type: text/plain; charset="iso-8859-1" From: "Michael O'Henly" Reply-To: michael@tenzo.com To: Alex Varju Subject: Re: FreeBSD Port: jpilot-0.99_2 Date: Sun, 13 May 2001 12:32:10 -0700 X-Mailer: KMail [version 1.2] Cc: ports@FreeBSD.org References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01051312321000.02116@h24-69-46-74.gv.shawcable.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday 13 May 2001 12:15, Alex Varju wrote: > On Sat, 12 May 2001, Michael O'Henly wrote: > > 1. The first time I ran it, it was using a grey background (which is what > > I want). The second time, although I didn't select a different > > background, it switched to a really grotty purple. Each of the provided > > jpilotrc.[colour] files is displayed in the Prefs menu controlling > > background colour, so I know jpilot is seeing them -- but I can't switch > > to anything other than purple! > > I've tried copying the jpilotrc.[colour] files into my ./jpilot directory > > and I've tried changing ownership and permissions on these files in the > > share directory. > You should be able to go to File -> Preferences -> Settings and choose a > GTK colors file from the dropdown list. I would guess that the > jpilotrc.default colour scheme is what you were using. Sigh. Of course, this morning it works perfectly. ;-) Honestly, I fiddled with this for a good forty-five minutes last night and could not change the background colour... > > 2. Installing from the port puts jpilot's files into an odd location: > > /usr/local/pilot > > Why would the install not place jpilot's stuff in the existing /usr/local > > hierarchy? Like so: > This seems to be the convention for the pilot ports ... they all install > into /usr/local/pilot. Maybe somebody else could comment in more detail. Well, that's interesting. Jpilot is the first palm port I've installed so I didn't realize that it was the convention. But then I installed pilot-xfer and it went to the same location. This does seem odd since it involves creating a number of non-palm-related directories like /usr/local/pilot/share/emacs/site-lisp, etc., as well as making it necessary to add /usr/local/pilot/bin to the PATH. Thank you very much for your reply (and for porting jpilot!)... M. -- Michael O'Henly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message