From owner-freebsd-ports@FreeBSD.ORG Wed Sep 24 16:06:35 2008 Return-Path: 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 310DD1065692 for ; Wed, 24 Sep 2008 16:06:35 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id 0E4D38FC1E for ; Wed, 24 Sep 2008 16:06:35 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id CBED15C2D; Wed, 24 Sep 2008 12:06:33 -0400 (EDT) Date: Wed, 24 Sep 2008 12:06:33 -0400 From: Wesley Shields To: Josh Carroll Message-ID: <20080924160633.GC30745@atarininja.org> References: <8cb6106e0809240828v3ebe1095w898597fea2d40272@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8cb6106e0809240828v3ebe1095w898597fea2d40272@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-ports@freebsd.org Subject: Re: new reconfig-recursive target for 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: Wed, 24 Sep 2008 16:06:35 -0000 On Wed, Sep 24, 2008 at 11:28:43AM -0400, Josh Carroll wrote: > All, > > Note: I'm not currently subscribed to ports@, please cc: me on replies. > > I was wondering what peoples' thoughts are on a "reconfig-recursive" > target for ports? Basically, the same as config-recursive, but instead > of using config-conditional for each dependency, it would use config. > This might be useful for someone who wants to review dependecies' > options and/or make changes, but without having to manually iterate > through them or rmconfig-recursive first. > > I figured this might come in handy. Thoughts? Seems like a rare case where someone would want to re-visit (in this manner) options they have already set. That said, it may come in handy. I think "config-recursive-unconditional" would be a better name as it fits better with the "config-recursive" target. Of course, this is just a bikeshed argument so I don't care what it ends up being called. ;) -- WXS