From owner-freebsd-hackers  Sat May 27 23:58:43 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA01938
          for hackers-outgoing; Sat, 27 May 1995 23:58:43 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA01930
          for <hackers@FreeBSD.org>; Sat, 27 May 1995 23:58:41 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id XAA07439; Sat, 27 May 1995 23:53:55 -0700
Date: Sat, 27 May 1995 23:53:55 -0700
Message-Id: <199505280653.XAA07439@silvia.HIP.Berkeley.EDU>
To: alexis@unicorn.ww.net
CC: hackers@FreeBSD.org
In-reply-to: <199505272021.AAA23918@unicorn.ww.net> (alexis@unicorn.ww.net)
Subject: Re: /usr/local filetree and ports question
From: asami@CS.Berkeley.EDU (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=)
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

I think questions like this are more well-suited to the "ports" list,
Alexis....

 * 	My knowledges may be out of date, but every FreeBSD port I saw
 * before used /usr/local/lib directory for its libraries. The question is
 :
 * 	The thing described above would, as I suppose, enhace the structure
 * of the whole FreeBSD.

I agree with you, it's just that we are try to minimize the changes
necessary to the original source to make upgrades and stuff easier.
This means following the original's directory structures (as long as
they are in /usr/local or /usr/X11R6), and this usually means
/usr/local/lib for the libraries, architecture independent or not.

It's really not any philosophical decision on our part.  But with
nearly 300 ports out there, holding the upgrade headaches to a minimum
has a very high priority to us. ;)

Satoshi