portindex ignores (filters out) unchanged port

Joshua Root jmr at macports.org
Mon Dec 28 06:44:00 PST 2015


On 2015-12-29 00:33 , Mojca Miklavec wrote:
> Somewhat off-topic: One problem that I'm often experiencing is that
> PortIndex doesn't *remove* the port from the index.
> 
> Example: I created a new port under "sysutils" without checking
> whether such a port already existed in MacPorts. In fact that port was
> already under "lang" and I suddenly had two port with the same name
> under two categories. I removed the one I created, but I wasn't able
> to do anything with the old port.
> 
> The only recovery I was able to come up with was deleting PortIndex,
> but that meant waiting for that horrible p5-graveyard to finish the
> work.
> 
> Am I the only one experiencing the problem that entries don't get
> removed from the index once the files are gone?

In this situation, the newer Portfile gets indexed and replaces the
entry for the older one. After you delete the duplicate, you usually
have to touch the remaining one so it is newer than the PortIndex.

- Josh


More information about the macports-dev mailing list