From owner-freebsd-ports@FreeBSD.ORG Thu Feb 9 07:18:37 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0791A16A420 for ; Thu, 9 Feb 2006 07:18:37 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 7350A43D45 for ; Thu, 9 Feb 2006 07:18:36 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 41457 invoked by uid 399); 9 Feb 2006 07:18:35 -0000 Received: from localhost (HELO ?192.168.1.102?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 9 Feb 2006 07:18:35 -0000 Message-ID: <43EAECCB.3030407@FreeBSD.org> Date: Wed, 08 Feb 2006 23:18:35 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Jiawei Ye References: <43D610B6.5080008@FreeBSD.org> <20060203065504.GA3857@weller-fahy.com> <43E31808.6070205@FreeBSD.org> <20060203111911.GA22446@hal.ebs.gr> <43E84A10.2050201@FreeBSD.org> <43E86940.7070302@ebs.gr> <43E9024F.3040703@FreeBSD.org> <43E90C24.2000908@ebs.gr> <43EAE7BA.7010403@FreeBSD.org> <43EAE825.6010207@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Panagiotis Astithas , freebsd-ports@freebsd.org Subject: Re: New /bin/sh based script to manage ports 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: Thu, 09 Feb 2006 07:18:37 -0000 Jiawei Ye wrote: > Hi, > > What is the syntax for the portup.rc file? I have lots of options set > for my various installed ports, how do I convert them to portmaster > style? That's a reasonable question, but I should point out at the outset that I have not tried to match portupgrade feature for feature with portmaster. This script has grown organically as I needed new features; or as users have requested features after I introduced the script to "the public." :) Thus, I have not attempted to reproduce portupgrade's feature of per-port build options. I think that this is an interesting idea, and I'm certainly not opposed to adding it if enough people who would want to use portmaster otherwise tell me that this is a critical feature for them. However, I personally put options that I care about in /etc/make.conf. I also keep hoping that our OPTIONS framework will continue to be refined, and that more ports will use it. Do you see this issue (per-port options) as a critical one? On the other hand, if the question that you're asking is actually "How do I write a portmaster.rc file to always include certain options for portmaster?" then the syntax would be the same as the similar support in mergemaster. Take a look at the getopts statement in portmaster, and add something like: ALWAYS_SCRUB_DISTFILES=yes to either /etc/portmaster.rc, or $HOME/.portmasterrc. > Also, one thing I miss from portupgrade is the ability to deinstall > some port alone with ports that depend on it. Can that be added as > well? something like pkg_deinstall -r/R stuff? Interesting idea. To make sure that I understand your request, let's say I have a port foo, and in /var/db/pkg/foo-0.0.0.1 there is a +REQUIRED_BY file that lists several other ports. You want to be able to say 'portmaster -R foo' and have it deinstall all the ports listed in that +REQUIRED_BY file, then deinstall foo? If so, I think that should be relatively easy to do, I'll take a look at it. Doug -- This .signature sanitized for your protection