From owner-freebsd-ports@FreeBSD.ORG  Sun Jan 20 16:24:34 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 2BD6216A420
	for <freebsd-ports@freebsd.org>; Sun, 20 Jan 2008 16:24:34 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 7272213C461;
	Sun, 20 Jan 2008 16:24:33 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <479375C0.30507@FreeBSD.org>
Date: Sun, 20 Jan 2008 17:24:32 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: P Bielecki <pawciobiel@gmail.com>
References: <2e420cc20801200650q19ed0d03h38a3152b26f22643@mail.gmail.com>
In-Reply-To: <2e420cc20801200650q19ed0d03h38a3152b26f22643@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-ports@freebsd.org
Subject: Re: packages with security vulnerabilities
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2008 16:24:34 -0000

P Bielecki wrote:
> Hi,
> 
> freebsd-update helps me update base system,
> portaudit(1) reminds me everyday about security vulnerabilities in
> ports/packages and thanks to portupgrade(1),
> I keep them up to date.
> 
> Quite often I build packages or use packages whenever available and
> share (NFS) them with my other boxes.
> 
> Although building and "deploying" packages can be fairly simple,
>  due to dependencies, slow network connections, hw problems or just
> slow machine it takes a while.
> 
> What would really help me is if  latest - updated packages could be
> available more often.
> 
> How porters decide which package should be updated and available as package?
> Is there anything what can I do to help updating latest packages?

Packages are built continuously and as fast as possible.  Which package 
sets do you feel are being updated too slowly?

Kris