From owner-freebsd-ports  Tue Sep 26 00:48:02 1995
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA22584
          for ports-outgoing; Tue, 26 Sep 1995 00:48:02 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA22579
          for <ports@freebsd.org>; Tue, 26 Sep 1995 00:47:59 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA17449; Tue, 26 Sep 1995 00:47:50 -0700
Date: Tue, 26 Sep 1995 00:47:50 -0700
Message-Id: <199509260747.AAA17449@silvia.HIP.Berkeley.EDU>
To: scott@statsci.com
CC: ports@freebsd.org
In-reply-to: <m0swHIh-000r3tC@main.statsci.com> (message from Scott Blachowicz on Fri, 22 Sep 1995 16:14:32 -0700)
Subject: Re: which releases are /pub/FreeBSD/packages/* good for?
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
Precedence: bulk

 * Is the packaging scheme smart enough to tell if I have a suitable OS revision
 * for being able to use a particular package? For instance, if I go grab 
 * ftp.freebsd.org:/pub/FreeBSD/packages/All/zsh-2.6b10.tgz and am able to 
 * successfully pkg_add it, should I expect that it will work properly? I'm 
 * running 2.0.5-RELEASE from CD. Or should I just go grab sources & build for 
 * myself? Or should I just be patient and wait for the 2.1 CD?

 @ No, that's why we build packages in a batch in put them in
   package-<rel> directories.

 @ It depends, it should complain about the libc minor version number but 
   zsh will probably work.

 @ Yes, that's probably the best idea at this point.  With the ports
   mechanism, building the software yourself is almost as easy as
   adding it from a package.

 @ That's a good idea too. :)

Satoshi