From owner-freebsd-ports  Thu May  2 01:39:14 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA06570
          for ports-outgoing; Thu, 2 May 1996 01:39:14 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA06562
          for <freebsd-ports@freebsd.org>; Thu, 2 May 1996 01:39:10 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id BAA06570; Thu, 2 May 1996 01:37:32 -0700 (PDT)
Date: Thu, 2 May 1996 01:37:32 -0700 (PDT)
Message-Id: <199605020837.BAA06570@silvia.HIP.Berkeley.EDU>
To: knarf@camelot.de
CC: freebsd-ports@freebsd.org
In-reply-to: <4m9peo$hf0@lancelot.camelot.de> (knarf@camelot.de)
Subject: Re: -current-ports under -RELEASE
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * I usually use the -current-ports under 2.1.0-RELEASE, because I want
 * to stay up to date. This ususally works fine, but there are some ports
 * (top, ssh, ...), which don't compile under -RELEASE.

That's why it's under -current. :)

 * I think the -current-ports should work under the _latest_ release and
 * if that is not possible, there should be a flag or something which
 * says it is impossible to compile this port under -RELEASE, perhaps
 * with a small explanation...

It is not possible, unless someone volunteers to take care of
synchronizing the two port trees.  I'm stumped with the -current tree.

Satoshi