Date: Sun, 19 Feb 2006 21:28:35 +0300 From: "Andrew Pantyukhin" <infofarmer@gmail.com> To: gerard@seibercom.net Cc: freebsd-questions@freebsd.org Subject: Re: Duplicate INDEX entry Message-ID: <cb5206420602191028x7324b313m672cf4eaf7f68a6a@mail.gmail.com> In-Reply-To: <200602191034.17283.gerard@seibercom.net> References: <200602191034.17283.gerard@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/19/06, Gerard Seibert <gerard@seibercom.net> 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 <format:bdb1_btree> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420602191028x7324b313m672cf4eaf7f68a6a>