From owner-freebsd-ports@FreeBSD.ORG Thu Feb 9 07:41:32 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 1F1BF16A420 for ; Thu, 9 Feb 2006 07:41:32 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9563143D46 for ; Thu, 9 Feb 2006 07:41:30 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by wproxy.gmail.com with SMTP id i13so242998wra for ; Wed, 08 Feb 2006 23:41:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EDpAYGwMdZx9Eq3dnrHVIfnGYcbsSTDQK8WgwdqAXMI7dRpv0gZ50dtxdA5iaMkyuC7NtVoK7w2Kr15J9KgaBd1Nr0R7FfyutXN1IkeF2dmrypHoz2yAjwE1J6DiVVN5j65YtoBiGO5JIN90Q1jc93WfsD/3jatl+vXO4OYsO0w= Received: by 10.65.150.19 with SMTP id c19mr2157998qbo; Wed, 08 Feb 2006 23:41:29 -0800 (PST) Received: by 10.65.107.16 with HTTP; Wed, 8 Feb 2006 23:41:29 -0800 (PST) Message-ID: Date: Thu, 9 Feb 2006 15:41:29 +0800 From: Jiawei Ye To: Doug Barton In-Reply-To: <43EAECCB.3030407@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43D610B6.5080008@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> <43EAECCB.3030407@FreeBSD.org> 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:41:32 -0000 On 2/9/06, Doug Barton wrote: > 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 h= ave > 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 m= ore > ports will use it. Do you see this issue (per-port options) as a critical= one? The problem with options in make.conf is that there might be namespace problems. To deal with that, some .dir boiler plate is needed, and when you have 300+ ports installed, make.conf may be very messy. If portmaster can grow the ability to specify per-port options, that will be a great plus.(like pkgtools.conf or portmanager/pm-020.conf style config files). I started on portupgrade and now use portmanager to manage my ports. Having a centralized tool to manager/install/deinstall my ports/package is important to me. I am not against the idea of using OPTIONS for ports, but it will be fairly cumbersome when one just needs a quick glance at the whole picture of different per-port options of the installed ports. > > 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 f= ile > 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 Exactly. I used to do "pkg_deinstall -rR qt" when either me or qt did not behave. One example what pkg_deinstall does extremely well is, say you have 4 ports foo1 foo2, foo3, foo4. foo1 is required by foo2, foo3. foo2 is required by foo4. "pkg_deinstall -rR foo2" will only remove foo4 and foo2, but not foo1 since foo3 requires foo1 too. Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming