From owner-freebsd-ports@FreeBSD.ORG Thu Jan 8 21:30:27 2004 Return-Path: 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 C39FA16A4CE for ; Thu, 8 Jan 2004 21:30:27 -0800 (PST) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CF0243D2F for ; Thu, 8 Jan 2004 21:30:26 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i095UPAI032306; Fri, 9 Jan 2004 00:30:25 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040109052019.GA8007@Odin.AC.HMC.Edu> References: <20040109052019.GA8007@Odin.AC.HMC.Edu> Date: Fri, 9 Jan 2004 00:30:24 -0500 To: Brooks Davis From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-ports@freebsd.org Subject: Re: Call for feedback on a Ports-collection change X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 05:30:27 -0000 At 9:20 PM -0800 1/8/04, Brooks Davis wrote: >On Fri, Jan 09, 2004, Garance A Drosihn wrote: > > Inside the proposed pkg-data file, the patches can have >> whatever names you want. (That was already part of my >> plan). For instance, you could name each patch for the >> exact filename it modifies (if you wanted to) -- including >> directory names and using '/'s as separators. It's just >> that when the program spits them out, it'll do it into >> boring-named files. That was my thought, at least, I'm >> certainly willing to spit them out with other names. > >What I'd really like to see from you is, what does the port >maintanence cycle look like to the port maintainer and how >is it different from today. I can think of different ways >it would work, but I want to know how you see it happening. Basically, I don't have a finalized idea on that. That's the kind of feedback that I need from developers who are more experienced with ports than I am. From other comments in this thread, I'm thinking that maybe I need some kind of "export" and "import" option on the simple-program for managing the pkg-data file. So (maybe) you would: 1) run: pdatamgr export patches which would create a directory that has all the patches in the present patch file. 2) make whatever changes you want to make. 3) run: pdatamgr import patches and the program pulls those patches into the pkg-data file. 4) run: cvs commit pkg-data but really, I'm open to other ideas. This project has plenty of work to keep me busy before I need to write that code. >One thing I like about the idea of stuffing the patches into >some sort of single file is that it would actually reduce the >amount of information I have to put in PRs since path addition >and removal would just happen. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu