Ports with a wrong PKGORIGIN

[Oliver Eikemeier]

Pav Lucistnik wrote:

> Suggestion to eik: what about mailing ports-developers@ instead of
> ports@? I read ports-developers immediately, but ports@ only once in
> a while.

I'm happy with that, since only ports committers can do something to
fix this anyway. OTOH, the same rationale that are valid for a
broken INDEX apply to PKGORIGIN and PKGVERSION: Port users might want
to know that the will run into trouble when they are trying to
update the port, and CCing ports-developers seems overambitious.


Any thoughts?

-Oliver