From owner-freebsd-ports  Fri Mar 22 09:37:18 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA17475
          for ports-outgoing; Fri, 22 Mar 1996 09:37:18 -0800 (PST)
Received: from covina.lightside.com (covina.lightside.com [198.81.209.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA17470
          for <freebsd-ports@freebsd.org>; Fri, 22 Mar 1996 09:37:16 -0800 (PST)
Received: by covina.lightside.com (Smail3.1.28.1 #6)
	id m0u0Alx-0004IyC; Fri, 22 Mar 96 09:37 PST
Date: Fri, 22 Mar 1996 09:37:06 -0800 (PST)
From: Jake Hamby <jehamby@lightside.com>
To: "Matthew N. Dodd" <winter@jurai.net>
cc: freebsd-ports@freebsd.org
Subject: Re: Pine 3.92
In-Reply-To: <Pine.BSF.3.91.960322084426.9008A-100000@sasami>
Message-ID: <Pine.AUX.3.91.960322093514.17623A-100000@covina.lightside.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 22 Mar 1996, Matthew N. Dodd wrote:

> Is there any good reason NOT to make shared libraries out of libpico.a
> and (lib)c-client.a?
> 
> I decided to hack on pine this morning instead of going to sleep and 
> I've pretty much got it working.
> 
> Any comments?  Should I make my diffs and submit a port?  Or am I
> sleep deprived and meddling things that are best left to more awake people?
> 
> 
> Have a good one.

As a general rule, I like to make shared libraries of _anything_ which 
will be used by two or more programs.  Therefore, I have libjpeg, 
libtiff, libpng, and libz all built as shared libraries for use by XV, 
Ghostscript, etc...  Since libpico is used by pico as well as pine, both 
programs that I use, I think it makes sense to build a shared library.  
Comments?

---Jake