From owner-freebsd-ports@FreeBSD.ORG Thu Dec 13 15:30:49 2007 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFB8716A419 for ; Thu, 13 Dec 2007 15:30:49 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id 7B62A13C457 for ; Thu, 13 Dec 2007 15:30:49 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.1/8.14.1) with ESMTP id lBDFUj8M051216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Dec 2007 10:30:45 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.14.1/8.14.1/Submit) id lBDFUitI051215; Thu, 13 Dec 2007 10:30:44 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: Philip Paeps , Bill Moran Date: Thu, 13 Dec 2007 10:30:44 -0500 User-Agent: KMail/1.9.7 References: <20071213024946.GA4959@soaustin.net> <200712130923.24488@aldan> <20071213143306.GA27297@soaustin.net> In-Reply-To: <20071213143306.GA27297@soaustin.net> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: ports@freebsd.org, Peter Jeremy Subject: Re: Ion3 removal X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2007 15:30:50 -0000 On =DE=C5=D4=D7=C5=D2 13 =C7=D2=D5=C4=C5=CE=D8 2007, Mark Linimon wrote: =3D Wrong. =9AYou do cvs add, cvs com. That would lose the prior history of the port, AFAIK. =3D At least in the US, a court of law won't accept "we'll be deleting the =3D infringing software Pretty Soon." =9AOnce notified of the infringement,= you =3D are obliged to take immediate action. =46ORBIDDEN prevents the port from being built just as immediately. You can= then=20 proceed to remove the already built packages from the ftp-site, which was=20 done anyway. It is perfectly clear from the thread(s) -- and most participants don't eve= n=20 deny it -- that the personal feelings towards Tuomo have hastened the port'= s=20 demise. Despite the ongoing port-freeze... I share some of the feeling, but we add/remove ports to improve the experie= nce=20 of users (including ourselves), not of the authors. =3D Keeping us legal is an explicit part of the portmgr charter. The surest thing to do so is to remove the entire ports collection -- it is= =20 all a major liability: http://technocrat.net/d/2006/6/30/5032 Tuomo's demands aren't unheard of either -- Sun's requirement, that Java=20 binaries be "certified" isn't that different... And, unlike Tuomo, they=20 already have brought a major lawsuit against a license-violator. But we=20 continue to have JDK-ports (we just don't distribute the resulting=20 binaries)... Bill Moran wrote: =3D > should've been addressed by using FORBIDDEN/IGNORE instead. =3D Perhaps you're right. However, I'd like to hear the opinion of a lawyer =3D as to whether this is acceptable or not. The (mathematical) expectactions of the payments to lawyers equal the amoun= t=20 multiplied by the probability of having to pay. You are suggesting a paymen= t=20 of $200-$300 (for consultation) with the probability of 1 against the=20 $10K-20K multiplied by, uhm, something so close to zero, that it may not fi= t=20 in this message. If anybody ever does file a suit against FreeBSD, it will= =20 not be Tuomo. The thread has riched the sad point of tiring the readers regardless of=20 contents long ago, and the port-maintainer has finally chimed in saying, he= =20 is going to resurrect the port portmgr-permitting. The portmgr implied=20 permission already, so let's get back to coding. Tuomo Valkonen wrote: =3D However, there's still the problem of binary packages ending up in the =3D release snapshots without prominent notices of obsoleteness. So, like Java and others, let's mark this port (upon ressurection) RESTRICT= ED=20 and NO_CDROM so that binaries aren't distributed and the user always has to= =20 build from source -- but with the port's aid. The Xinerama can be among the= =20 OPTIONS (default off) thus respecting the requirement, that modifications b= e=20 only on user's request. -mi