Date: Tue, 10 Apr 2012 16:47:41 +0200 From: Pietro Cerutti <gahr@FreeBSD.org> To: araujo@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: <20120410144741.GC73185@gahrfit.gahr.ch> In-Reply-To: <CAOfEmZh82tEziiRgDSYkgiBuN-pxV-dOULCxR5K-LDxL029-RA@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--kfjH4zxOES6UT95V Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > 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. 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. > 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. 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. > 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. 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. --=20 Pietro Cerutti The FreeBSD Project gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp --kfjH4zxOES6UT95V Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk+ESA0ACgkQwMJqmJVx947+UQCgs7tk7eBZcI52xCD5Ntn+54Oc m2wAnid+1bfqh2GIg63OXwmbULdvWzOj =gTA9 -----END PGP SIGNATURE----- --kfjH4zxOES6UT95V--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120410144741.GC73185>