On 11/11/2011 14:15, Xin LI wrote:
> (I just picked one message to do a reply-all, not specific to any one
> single message but all of them).
>
> Technically speaking the current approach's problem is that the user
> might have no chance of seeing it before the port is removed.
That's going to be true no matter what approach we use, or what time
period we choose. There are plenty of boxes that just sit there happily
doing their work without being updated. If that's the case, then the
fact that a port is deprecated or removed isn't really a problem for
them. Vulnerable ports are a different issue, but we have portaudit for
that.
> By its
> nature, deprecated ports tends not to be updated for long time, port
> tools like portmaster, portupgrade will not even see it because no
> PORTREVISION bump happen.
portmaster -L will warn you about ports marked
DEPRECATED/FORBIDDEN/IGNORE/BROKEN if you run it against an updated
ports tree. One area where we actually can improve here is to also put
this information in the INDEX. I have an idea for that, just haven't
been able to put the time into making it happen.
> For users who install from packages, there
> is no deprecation message at all, and it's pretty likely that these
> user when updating to a new version suddenly find the software missing.
I would think that the lack of a package would be a pretty clear message
that there is an issue that needs attention, wouldn't you? :) Perhaps we
need to rethink the policy on whether packages should be created for
deprecated ports.
> I think if we want to deprecate ports in a constant manner, we need to
> do a better job of letting the user (or let's say potential
> contributor) know it.
I think you're right that we can do more, so what is your proposal?
Doug
--
"We could put the whole Internet into a book."
"Too practical."
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
