From owner-freebsd-questions@FreeBSD.ORG Sun Feb 19 18:28:37 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1992A16A420 for ; Sun, 19 Feb 2006 18:28:37 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id A467943D46 for ; Sun, 19 Feb 2006 18:28:36 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id f1so733676nzc for ; Sun, 19 Feb 2006 10:28:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=l/gNq+Qhg/oNgOTrWDrG3hrqeVSOwKvCb4k4usuADJQz/zOoAcdXm+h+sB49+5/6JlgET7ZrjVXYVAYOeiGORgHRW2hoXgpKIukNOsZlHOXnmVSEX6Lv4QbsYHO/85U5gBjKq+IvbhlD902HlCnu5A4nYmatZ9T7vZA1+I9wKc4= Received: by 10.36.140.6 with SMTP id n6mr4533598nzd; Sun, 19 Feb 2006 10:28:35 -0800 (PST) Received: by 10.37.20.11 with HTTP; Sun, 19 Feb 2006 10:28:35 -0800 (PST) Message-ID: Date: Sun, 19 Feb 2006 21:28:35 +0300 From: "Andrew Pantyukhin" To: gerard@seibercom.net In-Reply-To: <200602191034.17283.gerard@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200602191034.17283.gerard@seibercom.net> Cc: freebsd-questions@freebsd.org Subject: Re: Duplicate INDEX entry X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2006 18:28:37 -0000 On 2/19/06, Gerard Seibert wrote: > When running this command: portsdb -Uu, I am frequently presented with a > message similar to this one: > > portsdb -Uu > Updating the ports index ... Generating INDEX.tmp - please wait.. > Warning: Duplicate INDEX entry: apr-gdbm-db4-1.2.2_2 > Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.7 > Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 > Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 > Done. > done > [Updating the portsdb in /usr/ports ... - 14143 port > entries > > found .........1000.........2000.........3000.........4000.........5000..= ...... > .6000.........7000.........8000.........9000.........10000.........11000.= ....... > .12000.........13000.........14000. ..... done] > > I have checked the archives and found that this is not suppose to be a > serious problem. I was wondering that while this might not be a serious > problem, just why is it happening at all. Is there some method or > procedure to correct this phenomena, or can I just safely ignore it? Well, for one thing, it's the way master/slave ports work. Many slave ports just set a flag (like WITH_GTK2). If you already have this flag enabled in make.conf the two ports are effectively identical. In general, such slave ports only appear because of the inflexibilities of the ports system. Their presence is not really a Bad Thing in the absence of a better solution.