From owner-freebsd-ports@FreeBSD.ORG Fri Jul 27 06:08:56 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 B6C1A16A41F for ; Fri, 27 Jul 2007 06:08:56 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id 6E36B13C49D for ; Fri, 27 Jul 2007 06:08:56 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 10733 invoked from network); 27 Jul 2007 01:08:55 -0500 Received: from 203-206-233-219.dyn.iinet.net.au (HELO localhost) (203.206.233.219) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Jul 2007 01:08:55 -0500 Date: Fri, 27 Jul 2007 16:08:51 +1000 From: Norberto Meijome To: Kurt Abahar Message-ID: <20070727160851.31e6a8a7@localhost> In-Reply-To: <667520.17083.qm@web53511.mail.re2.yahoo.com> References: <46A94E00.8090806@FreeBSD.org> <667520.17083.qm@web53511.mail.re2.yahoo.com> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: Keeping Ports and Packages Synchronized 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: Fri, 27 Jul 2007 06:08:56 -0000 On Thu, 26 Jul 2007 21:21:01 -0700 (PDT) Kurt Abahar wrote: > Side note: I'm asking because I would definitely be > willing to contribute since this would make using > ports and packages together much easier. I think the issue is one of building tens of thousands of applications and ensuring they are valid. the process exists already in the ports build farm (not sure what it is really called), but as you can see it lags behind individual ports updates. Anyway, as Chuck said , you can't always use a binary pkg as they may not suit your needs. > I also think > that such a configuration would be a better default > for portsnap. Portsnap's functionaty is to update the ports tree, not the binary packages. I am not sure you'd want to have a 'pkgsnap' in all your machines.. that would effectively mean you are providing a mirror for all built packages... B _________________________ {Beto|Norberto|Numard} Meijome "The freethinking of one age is the common sense of the next." Matthew Arnold I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.