Date: Tue, 10 Apr 2012 12:14:23 -0300 From: Marcelo Araujo <araujobsdport@gmail.com> To: gahr@freebsd.org Cc: bapt@freebsd.org, ports-committers@freebsd.org, ports@freebsd.org, Frederic Culot <culot@freebsd.org>, cvs-ports@freebsd.org, Mark Linimon <linimon@lonesome.com> Subject: Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-clx-sbcl Makefile ports/palm/coldsync ... Message-ID: <CAOfEmZg-4WPvBJacaQQOwS%2BU04Mkk%2B7wQ8L0qXdUxi6mj6aSpQ@mail.gmail.com> In-Reply-To: <20120410144741.GC73185@gahrfit.gahr.ch> References: <201204092351.q39Npi6F025202@repoman.freebsd.org> <20120410091537.GK98668@gahrfit.gahr.ch> <20120410114537.GL17460@culot.org> <20120410115630.GB2456@lonesome.com> <CAOfEmZgaagMqBq_690E9a4yo=vJ6Lnet-PAOrHi6c8e2xpfrTA@mail.gmail.com> <20120410124449.GB73185@gahrfit.gahr.ch> <CAOfEmZh82tEziiRgDSYkgiBuN-pxV-dOULCxR5K-LDxL029-RA@mail.gmail.com> <20120410144741.GC73185@gahrfit.gahr.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
2012/4/10 Pietro Cerutti <gahr@freebsd.org> > On 2012-Apr-10, 11:20, Marcelo Araujo wrote: > > 2012/4/10 Pietro Cerutti <gahr@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 agree on that. > > > > > I believe set it as DEPRECATED is a good way to make the maintainer tak= e > > attention to fix it soon as possible, due he has put effort to insert > this > > software on the ports tree in the past. > > What about submitting a PR, as we usually do for anything else? If it's > ok to wait 15 days (maintainer timeout) to commit an update to a port > that brings in important features, it is even more so to wait to > deprecate one. > That is a very good point, if someone send a PR, nobody need to make it DEPRECATED, but unfortunately, sometimes it doesn=92t happens. And as I can see, almost all ports that switch from BROKEN to DEPRECATED, is because no one send a PR. > > > In case that has any issue related with the ports framework that make t= he > > 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. > > This is awkward. We're not supposed to spend our time rolling back > unwanted commits. We're supposed to make sure that a commit made to > someone else's port is wanted in the first place. > I agree with you, maybe there is another better way. > > > It also will let us know, what's happen with that port and maybe someon= e > > else could give a hand to help the maintainer to fix it. > > Well, as I see it, marking a port as DEPRECATED is kind of a final > decision. I.e., I'll start to look at alternatives and forget about it. > If you mark a port as DEPRECATED and 12 hours later I back off your > chance with a comment "I'm working on it", a really unconsistent and > confused message will pass. > Here depends! Usually when I need a port that is set as DEPRECATED, first I take a look why it is set like this, and then, I start to looking for an alternative in case I can=92t fix that port or it is really obsolete becaus= e the software is dead for some reason. Best Regards, --=20 Marcelo Araujo araujo@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfEmZg-4WPvBJacaQQOwS%2BU04Mkk%2B7wQ8L0qXdUxi6mj6aSpQ>