From owner-freebsd-ports@FreeBSD.ORG Tue Nov 21 00:50:03 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83DCC16A416 for ; Tue, 21 Nov 2006 00:50:03 +0000 (UTC) (envelope-from eric@mikestammer.com) Received: from smtp101.sbc.mail.mud.yahoo.com (smtp101.sbc.mail.mud.yahoo.com [68.142.198.200]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F7F843D58 for ; Tue, 21 Nov 2006 00:49:41 +0000 (GMT) (envelope-from eric@mikestammer.com) Received: (qmail 3050 invoked from network); 21 Nov 2006 00:49:59 -0000 Received: from unknown (HELO mail.mikestammer.com) (mikestammer@sbcglobal.net@70.131.98.204 with login) by smtp101.sbc.mail.mud.yahoo.com with SMTP; 21 Nov 2006 00:49:59 -0000 X-YMail-OSG: CPtrWzQVM1kh7a0qinAplE._y99cf9bsk3EXUY6t.lXlXgemPOsu0uBhi8pE4XeDwSJ0og96Xv2kgt7VF2AczT2YKTTcPMoChrjoVS.MknOh5JFgywaABfKoj5dg_RHGi0nhOJVnSLCxnnCXPyJNHgJXAePn.HE2f7M- Received: from localhost (localhost [127.0.0.1]) by mail.mikestammer.com (Postfix) with ESMTP id 051311146A; Mon, 20 Nov 2006 18:49:58 -0600 (CST) X-Virus-Scanned: amavisd-new at mikestammer.com Received: from mail.mikestammer.com ([127.0.0.1]) by localhost (gondolin.middleearth.mikestammer.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5m7a7CidIQs; Mon, 20 Nov 2006 18:49:54 -0600 (CST) Received: from [192.168.0.20] (unknown [192.168.0.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eric) by mail.mikestammer.com (Postfix) with ESMTP id 4003A11465; Mon, 20 Nov 2006 18:49:53 -0600 (CST) Message-ID: <45624D29.4090808@mikestammer.com> Date: Mon, 20 Nov 2006 18:49:45 -0600 From: Eric User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Mark Ovens References: <4562415A.30106@freebsd.org> In-Reply-To: <4562415A.30106@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Question about portmanager(1) ownership 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: Tue, 21 Nov 2006 00:50:03 -0000 Mark Ovens wrote: > Can someone explain about the ownership of sysutils/portmanager please? > > It is obviously a FreeBSD-specific port (and I recognize the name > Michael Schultz as a member of the FreeBSD community) and the project > is hosted on SourceForge but the SF project pages seem way out of > date. Also, I submitted a patch in ports/98032 - to stop it dumping > core if run by a non-root user - which was committed, but as a patch > rather than a mod to the core code, which puzzles me since, as I said, > it is FreeBSD-specific. > > The reason I ask is that I want to do some more enhancements to it but > wondering where the project is at. > > I've got ~450 ports installed on my main system and I find the output > of ``portmanager -s'' a real PITA. It's unsorted (presumably the > output order is the order it walks the installed ports and their > dependencies?) meaning I have to scroll through 450 lines of output to > see if a particular port has been updated, e.g. if I'm waiting for a > fix to be committed. > > What I want to do is add an option/options to control/limit the > output. For example, choose how the output is sorted - by port name, > port collection (with name as the secondary sort), or status, plus > options to restrict the output to a particular status, mainly not > CURRENT, e.g. only list ports that are not CURRENT and sort the output > by name. This would make it a lot easier to find if > frobulators/widgetmangler has been updated. > > ``portmanager -s | grep -v CURRENT'' goes some way to achieving this, > but it would be better if there was more control. > > Thanks. > > Regards, > > Mark try portmaster, its way better IMO and actively developed.