From owner-freebsd-ports@FreeBSD.ORG Wed Mar 23 11:30:35 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F317106566B for ; Wed, 23 Mar 2011 11:30:35 +0000 (UTC) (envelope-from peterj@mister-j.dyndns.org) Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by mx1.freebsd.org (Postfix) with ESMTP id CABBA8FC14 for ; Wed, 23 Mar 2011 11:30:34 +0000 (UTC) Received: from [172.23.170.143] (helo=anti-virus02-10) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1Q2Lcr-0006IJ-Qp for freebsd-ports@freebsd.org; Wed, 23 Mar 2011 10:49:18 +0000 Received: from [92.232.234.6] (helo=fire.mister-j.org.uk) by asmtp-out3.blueyonder.co.uk with esmtpa (Exim 4.72) (envelope-from ) id 1Q2Lcf-0001tk-3X for freebsd-ports@freebsd.org; Wed, 23 Mar 2011 10:49:05 +0000 Received: by fire.mister-j.org.uk (Postfix, from userid 58) id 209D7E0958; Wed, 23 Mar 2011 10:49:04 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on fire.mister-j.org.uk X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham version=3.3.1 Received: from pete01.gateway.2wire.net (host81-130-91-96.in-addr.btopenworld.com [81.130.91.96]) by fire.mister-j.org.uk (Postfix) with ESMTPSA id 614A6E0913; Wed, 23 Mar 2011 10:48:57 +0000 (GMT) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "Henk van Oers" , "Zhihao Yuan" References: Date: Wed, 23 Mar 2011 10:48:58 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Peter Jeffery" Message-ID: In-Reply-To: User-Agent: Opera Mail/11.01 (Win32) Cc: freebsd-ports@freebsd.org Subject: Re: [HEADS UP] Ports Infrastructure Changes 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: Wed, 23 Mar 2011 11:30:35 -0000 On Sun, 20 Mar 2011 07:26:45 -0000, Zhihao Yuan wrot= e: > On Sat, Mar 19, 2011 at 5:29 PM, Henk van Oers wro= te: >> >> From: Pav Lucistnik >> >> Matthias Andree p=ED=B9e v so 19. 03. 2011 v 09:52 +0100: >> [...] >>>> >>>> Where do you see the dividing line between web apps on one hand and= on >>>> the other hand "http servers ... everything related to apache"? IO= W, >>>> how do I decide if I put a new port into www-webapps or into = >>>> www-servers >>>> for its primary category? >> >>> Basically, everything that serves network is "server" and everything= >>> that generates pages on these servers is "webapp". >> >> So: why is p5-Mojolicious in webapp, it serves network (main = >> deployment). >> And it's a client too... > > Not just p5-Mojolicious. Many webapps can be web servers, like Flask. > Even some unrelated packages can be www servers, like python, with > SimpleHTTPServer. And some www-clients can also be www-servers. For > example, opera. It's a client, server, email client, HTML-editor. You > can't just *separate* things into clients, servers, apps, and misc. I would say that although it is correct to say that something like Opera= is all of those things you should think about the main way in which the application is perceived. If I was looking for the Opera port, I'd look in www-clients and if it = wasn't in there then the next thing that I would be doing is hand searching the= = INDEX file, because I'd have no idea where else it might be. I shouldn't need to know its full in depth feature set just so that I ca= n = find it to install it. > And also, during the development of the HTML5, there will be more and > more www-client ports can be used as servers, by using web socket. The= > border of clients and servers will become fuzzy. We should not used a > C/S model to sort these ports. > > That's why I suggest that to create a www-devel branch - you can > determined what a software is mainly designed for, but you can not > always determined what a software can be used as. > >> >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.o= rg" >>