From owner-freebsd-ports@FreeBSD.ORG Mon Aug 25 19:39:23 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E75BF665; Mon, 25 Aug 2014 19:39:22 +0000 (UTC) Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA053358; Mon, 25 Aug 2014 19:39:21 +0000 (UTC) X-Trace: 122965123/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$ON_NET_AUTH_ACCEPTED/pipex-temporary-group/81.170.79.154/-4.0/crees@physics.org X-SBRS: -4.0 X-RemoteIP: 81.170.79.154 X-IP-MAIL-FROM: crees@physics.org X-SMTP-AUTH: bayofrum@uwclub.net X-MUA: K-9 Mail for Android X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As8HAGSQ+1NRqk+aPGdsb2JhbABagw1TV4J8x3uBX4dRAYEiFwUBAQEBODaEBAEBBCMPASMjEAsEFCoCAiEYChQGAQ0FiC4DFasdjzkNhSIXiX8vgnGBSRMBASkmBwmCcIFTBZVPhGqCEIFYhT+HQAKKEjwvgQYJF4EpAQEB X-IPAS-Result: As8HAGSQ+1NRqk+aPGdsb2JhbABagw1TV4J8x3uBX4dRAYEiFwUBAQEBODaEBAEBBCMPASMjEAsEFCoCAiEYChQGAQ0FiC4DFasdjzkNhSIXiX8vgnGBSRMBASkmBwmCcIFTBZVPhGqCEIFYhT+HQAKKEjwvgQYJF4EpAQEB X-IronPort-AV: E=Sophos;i="5.04,398,1406588400"; d="scan'208,217";a="122965123" X-IP-Direction: OUT Received: from 81-170-79-154.dynamic.dsl.as9105.com (HELO pegasus.bayofrum.net) ([81.170.79.154]) by smtp.pipex.tiscali.co.uk with ESMTP; 25 Aug 2014 20:39:19 +0100 Received: from android-9c6e4780531e1a1d.bayofrum.net (android-9c6e4780531e1a1d.bayofrum.net [192.168.1.123]) by pegasus.bayofrum.net (Postfix) with ESMTPSA id A8A11617C9; Mon, 25 Aug 2014 20:39:17 +0100 (BST) User-Agent: K-9 Mail for Android In-Reply-To: References: <53FB5C74.2010409@physics.org> <53FB620A.1040603@marino.st> <53FB67B9.9040003@marino.st> <53FB6FE7.90701@ohlste.in> <53FB71B4.4090703@marino.st> MIME-Version: 1.0 Subject: Re: Return ports www/sams From: Chris Rees Date: Mon, 25 Aug 2014 20:39:16 +0100 To: zlopi ,marino@freebsd.org Message-ID: X-bayofrum-MailScanner-Information: Please contact the ISP for more information X-bayofrum-MailScanner-ID: A8A11617C9.A4015 X-bayofrum-MailScanner: Found to be clean X-bayofrum-MailScanner-From: crees@physics.org X-Spam-Status: No Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2014 19:39:23 -0000 Hi John, It seems to me that this might have been better just put in as an update to www/sams. Zlopi, please would you try out sams2 and let us know if it just works the same? That could render this whole discussion pointless! Chris On 25 August 2014 19:56:11 BST, zlopi wrote: >It makes me sad to look at how changes in recent years FreeBSD - not >for the better. >New packages - it's good. But! Stable packages replaced by new >unstable version - this is wrong. > >Thanks for taking your time on me. > >2014-08-25 21:26 GMT+04:00 John Marino : >> On 8/25/2014 19:18, Jim Ohlstein wrote: >>> Not for nothing, but since PHP 5.3 is still in the ports tree, then >why >>> delete ports that depend on it? I know PHP 5.3 has now reached EOL, >but >>> there is probably still a fair amount of legacy code which breaks >with >>> PHP 5.4. I'm not advocating using it, but some people have no >choice. If >>> people want it in the ports tree and they understand the risks, >>> shouldn't it be their choice? >> >> When it was deleted, the port claimed that it *only* worked with >PHP4. >> It was only after the deletion that somebody said it would work with >> 5.3. At that point we weren't bringing back an long-time >unmaintained >> port for a PHP that is probably itself on it's way out. Unmaintained >at >> the ports level *and* upstream. >> >> If these users really want to accept risk, they can always put a copy >of >> www/sams locally in their tree. >> >> www/sams2 is supposed to work with PHP 5.3, 5.4, and 5.5. Until I >hear >> why it's not a suitable replacement for an unmaintained sams, I don't >> understand why this discussion is happening at all. >> >> John > >-- >This message has been scanned for viruses and >dangerous content by MailScanner, and is >believed to be clean. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.