From owner-cvs-ports@FreeBSD.ORG Mon Aug 15 00:09:34 2011 Return-Path: Delivered-To: cvs-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A90901065677; Mon, 15 Aug 2011 00:09:34 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from fallbackmx06.syd.optusnet.com.au (fallbackmx06.syd.optusnet.com.au [211.29.132.8]) by mx1.freebsd.org (Postfix) with ESMTP id 2ED1D8FC0C; Mon, 15 Aug 2011 00:09:33 +0000 (UTC) Received: from mail26.syd.optusnet.com.au (mail26.syd.optusnet.com.au [211.29.133.167]) by fallbackmx06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p7EM0def007426; Mon, 15 Aug 2011 08:00:39 +1000 Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail26.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p7EM0Um3016184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Aug 2011 08:00:32 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p7EM0SWD030123; Mon, 15 Aug 2011 08:00:28 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p7EM0SS5030122; Mon, 15 Aug 2011 08:00:28 +1000 (EST) (envelope-from peter) Date: Mon, 15 Aug 2011 08:00:27 +1000 From: Peter Jeremy To: Dmitry Marakasov Message-ID: <20110814220027.GA29836@server.vk2pj.dyndns.org> References: <201108020942.p729g1Ti068765@repoman.freebsd.org> <20110811180338.GB88978@hades.panopticon> <20110812093328.GE85247@hades.panopticon> <20110812101133.GF85247@hades.panopticon> <4E4584EA.7090306@FreeBSD.org> <20110813133717.GA38385@hades.panopticon> <4E469837.1030903@FreeBSD.org> <20110813172040.GC38385@hades.panopticon> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20110813172040.GC38385@hades.panopticon> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/cad/admesh Makefile X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2011 00:09:34 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Aug-13 21:20:40 +0400, Dmitry Marakasov wrote: >You can't judge the quality of software by "it is maintained" or >"it is the latest version" either, actually there is no corellation >at all. There is very little bug-free software available. And even if you manage to find a piece of software that is bug-free, changes to its dependencies can introduce problems as interfaces change. > For the security, we have portaudit. I can only assume this statement is a joke. The vulnerability list that portaudit relies on in manually maintained - it's generally up to port maintainers to update this list. If there isn't a maintainer, it's unlikely that vulnerabilities will be reported. >> Possibly we should always mark ports for removal for three months after >> the point in time when the maintainer gets reset to ports@. Three months might be a bit soon but I think it would be a good idea for the ports build infrastructure to warn about unmaintained ports - eg building/installing it gives a message "warning: this port is unmaintained, it may not be up-to-date and may include unreported vulnerabilities" as well as an "unmaintained packages you have installed" report in periodic/weekly. With the current system, it's not obvious that pors are unmaintained. >Nice. Well that'll only result in two processes: more and more ports >will have maintainers reset and then removed, and remaining maintainers >will take more and more ports beyond their ability to maintain them, >both will lead to collapse. Is this also not undesirable? As you would be aware, committers !=3D maintainers. And it's difficult to see how fewer ports translates to more load on the committers. > And now I wonder what should I say >if a user asks why $port he wants doesn't build becase $dependent_port >is marked 'does not fetch' even after he downloaded the distfile >on his own? Maybe there needs to be an "UNFETCHABLE" variable that expands to "BROKEN=3Dunfetchable" unless the distfile is already present. > "FreeBSD guys don't want you to use this ports, sorry, go >away or fix it". That is what I call a nice attitude. And that's not what is meant. If that's the way you are responding to such questions, it is not really helping. Note that you are one of the "FreeBSD guys" that you disparage. >Also there had been a huge article an a discussion thread on "Key >FreeBSD problems and a way to solve them" after Rambler and Yandex >(largest FreeBSD using companies in Russia) decided to switch from >FreeBSD to Linux, which also mentions port problems and, which is >much worse, an attitude like yours. Let me translate an excerpt: Your excerpt does not mention ports and raises issues that are far more wide ranging. It needs to be discussed separately in a more appropriate forum. >A bit of constructive. While writing this I've got an idea: why >don't we introduce DEAD variable for this case? Yes. That sounds like a worthwhile idea. I'd suggest "DEAD" take a string that is presented to the user, rather than just producing a generic list of possibilities: =3D=3D=3D> foo-1.0 is marked as dead: No master site found You may still build this port on your own rish by adding TRYDEAD=3Dyes to make arguments or enironement. Note that dead port will be eventually removed from the ports tree if nobody steps forward to become its maintainer and/or fix it. --=20 Peter Jeremy --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5IRXsACgkQ/opHv/APuIdLBQCeP+/cFirAbLYzlJywpBfLwODI o40An3jBw3x0C+TEdNx82fhoIMTzUPg2 =mDD4 -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--