From owner-freebsd-ports@FreeBSD.ORG  Fri Jun 18 05:24:25 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C0EAB16A4CE
	for <ports@FreeBSD.org>; Fri, 18 Jun 2004 05:24:25 +0000 (GMT)
Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6484543D2F
	for <ports@FreeBSD.org>; Fri, 18 Jun 2004 05:24:25 +0000 (GMT)
	(envelope-from sem@ciam.ru)
Received: from msd.mbrd.ru ([194.117.71.30] helo=[172.16.4.9])
	by mail.ciam.ru with asmtp (Exim 4.x)
	id 1BbBqb-000ITL-RD; Fri, 18 Jun 2004 09:23:30 +0400
Message-ID: <40D27C4F.7000905@ciam.ru>
Date: Fri, 18 Jun 2004 09:23:27 +0400
From: Sergey Matveychuk <sem@ciam.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7) Gecko/20040514
X-Accept-Language: ru, en-us, en
MIME-Version: 1.0
To: Dan Langille <dan@langille.org>
References: <40D03202.11738.76559182@localhost>
In-Reply-To: <40D03202.11738.76559182@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: ports@FreeBSD.org
Subject: Re: HEADS UP - master/slave ports
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2004 05:24:25 -0000

Dan Langille wrote:
> http://beta.freshports.org/ now has support for displaying 
> master/slave relationships.  This is the first step in automatically 
> updating a slave port when a commit is made to a master port.  Until 
> recently, there was no acceptable method for determing master/slave 
> relationship.  Consequently, FreshPorts makes no attempt to refresh a 
> slave port when the master port is updated.

Well, it shows master/slave state for my ports right. But port versions 
are not equal. This part of work is not done yet?

---
Sem.