2012/4/10 Pietro Cerutti <g...@freebsd.org> > > > I might agree on that. But how is a DEPRECATED port better than a BROKEN > one in this regard? > > In my point of view, no make sense have a bunch of ports that actually doesn't works or because there is a fetch problem or even it is set as BROKEN. Who never was upset when need and find a port but it is BROKEN for some reason, In my view, have a port BROKEN or haven't it, is the same. Of course, I mean when a port is BROKEN for all plataforms as well as for all FreeBSD version.
I believe set it as DEPRECATED is a good way to make the maintainer take attention to fix it soon as possible, due he has put effort to insert this software on the ports tree in the past. In case that has any issue related with the ports framework that make the ports be broken, he can ping any developer to give him more time to fix or even rollback the DEPRECATED commit with a proper message on the commit's log. It also will let us know, what's happen with that port and maybe someone else could give a hand to help the maintainer to fix it. Best Regards, -- Marcelo Araujo ara...@freebsd.org _______________________________________________ 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"