From owner-freebsd-ports  Sat May 12 20:23: 6 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 97D8237B423
	for <ports@FreeBSD.org>; Sat, 12 May 2001 20:23:02 -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 f4D3Ptc11830;
	Sat, 12 May 2001 20:25:55 -0700 (PDT)
	(envelope-from michael@tenzo.com)
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Michael O'Henly" <michael@tenzo.com>
Reply-To: michael@tenzo.com
To: varju@webct.com
Subject: FreeBSD Port: jpilot-0.99_2
Date: Sat, 12 May 2001 20:25:55 -0700
X-Mailer: KMail [version 1.2]
Cc: ports@FreeBSD.org
MIME-Version: 1.0
Message-Id: <01051220255505.11355@h24-69-46-74.gv.shawcable.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi there...

I'm new to FreeBSD so my questions here may just be because I don't know what 
I'm doing. ;-)

I've installed your port and had no problems building it. I've run jpilot and 
all seems well. 

But...

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. 

2.  Installing from the port puts jpilot's files into an odd location:

/usr/local/pilot

Under this directory a whole hierarchy is created

/usr/local/pilot/bin
/usr/local/pilot/etc
/usr/local/pilot/include
/usr/local/pilot/info
/usr/local/pilot/lib
/usr/local/pilot/libdata
/usr/local/pilot/libexec
/usr/local/pilot/man
/usr/local/pilot/sbin
/usr/local/pilot/share

Why would the install not place jpilot's stuff in the existing /usr/local 
hierarchy? Like so:
 
/usr/local/bin
/usr/local/etc
/usr/local/include
/usr/local/info
/usr/local/lib
/usr/local/libdata
/usr/local/libexec
/usr/local//man
/usr/local/sbin
/usr/local/share

As I said, there's lots I don't know about FreeBSD so I'm just curious why it 
would work this way.

Thanks.

M.

-- 
Michael O'Henly

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message