From owner-freebsd-ports@FreeBSD.ORG Thu Feb 20 12:57:10 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 822B853B; Thu, 20 Feb 2014 12:57:10 +0000 (UTC) Received: from forward9l.mail.yandex.net (forward9l.mail.yandex.net [IPv6:2a02:6b8:0:1819::9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 26D701CCF; Thu, 20 Feb 2014 12:57:07 +0000 (UTC) Received: from smtp3h.mail.yandex.net (smtp3h.mail.yandex.net [84.201.186.20]) by forward9l.mail.yandex.net (Yandex) with ESMTP id C7F47E60DE6; Thu, 20 Feb 2014 16:57:02 +0400 (MSK) Received: from smtp3h.mail.yandex.net (localhost [127.0.0.1]) by smtp3h.mail.yandex.net (Yandex) with ESMTP id 3FD981B43605; Thu, 20 Feb 2014 16:57:02 +0400 (MSK) Received: from unknown (unknown [77.66.228.253]) by smtp3h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id B8k5RQuNSM-unimC9tb; Thu, 20 Feb 2014 16:57:01 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: 1c1537c4-11d3-4465-b2f5-45ed87bdea8e DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1392901021; bh=pcakfWRyeYfxq9O2PxQYu2vuZQZt31WTdebu3rvbsps=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=BhOdotWyhtv8jU44czdJhjkv0FwNEmvRrlHV6XAUU3H7jB5p8lUk/V9ac5f3dgDiE ss3ko9c7GAZaLNSKhyMK+Bd5F2o9tmd+ACm4O5mHfdyToGZPZRIg5/VfUD7zdDv3kd O/4M2Lbb88cZuWX/Wp3EwAf76mnZwriaCPPZJSYg= Authentication-Results: smtp3h.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5305FB84.3070103@yandex.ru> Date: Thu, 20 Feb 2014 16:56:36 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Ports Index build , ports@FreeBSD.org Subject: Re: Ports with duplicate LATEST_LINKs References: <201402201240.s1KCeVgr070805@portsindexbuild.ysv.freebsd.org> In-Reply-To: <201402201240.s1KCeVgr070805@portsindexbuild.ysv.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: brd@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Feb 2014 12:57:10 -0000 Ports Index build wrote on 20.02.2014 16:40: > Dear port maintainers, > > The following list includes ports maintained by you that have duplicate > LATEST_LINK values. They should either be modified to use a unique > PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is > deprecated. See the portmgr blog post for more information: > http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ > > > Thanks, > Erwin "Annoying Reminder Guy III" Lansing > > > LATEST_LINK PORTNAME MAINTAINER > ========================================================================== > liblogging sysutils/liblogging brd@FreeBSD.org > liblogging devel/liblogging ports@FreeBSD.org > Duplicate port has been added today in sysutils. May be it should be removed and devel/liblogging should be taken/updated instead. Adding sysutils port maintainer to Cc:. -- Regards, Ruslan T.O.S. Of Reality