From owner-freebsd-ports@FreeBSD.ORG Mon May 24 08:51:24 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 5776316A4CE for ; Mon, 24 May 2004 08:51:24 -0700 (PDT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0082A43D41 for ; Mon, 24 May 2004 08:51:24 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i4OFonIX003076; Mon, 24 May 2004 11:50:49 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040524133351.GA36711@regency.nsu.ru> References: <20040524133351.GA36711@regency.nsu.ru> Date: Mon, 24 May 2004 11:50:48 -0400 To: Alexey Dokuchaev 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: Third "RFC" on on pkg-data ideas for ports 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: Mon, 24 May 2004 15:51:24 -0000 At 8:33 PM +0700 5/24/04, Alexey Dokuchaev wrote: >On Mon, May 24, 2004, Garance A Drosihn wrote: > > c) [minor] in the pkg-data section for distinfo, I'd >> like to change the format for each file from, eg: >> MD5 (bash-2.05b.tar.gz) = 5238251b4926d778dfe162f6ce729733 >> SIZE (bash-2.05b.tar.gz) = 1956216 >> to > > 5238251b4926d778dfe162f6ce729733 1956216 bash-2.05b.tar.gz > >Hmm, this is gonna be hard for possible usage of non-MD5 hashing >schemes. See NetBSD pkgsrc collection for examples. Actually, I do expect to support other hashing schemes, but that is part of "future work", not "the initial project". There is more than one way to support them. If we use SHA-1 instead of MD5 for a port, for instance, then that first string will be longer. Or we could use a different section-name, which has different info and is formatted differently. Please note that the main idea here is to hide all those data-details in the program which processes these pkg-data files, and thus the main makefile rules would just say something like "verify bash-2.05b.tar.gz", and the program will decide what that means based on what the program finds in the pkg-data file. > > So it collapses most standard files into the pkg-data file, and >> collapses the patch-related files for a given port into files >> such as: ports/Patches/shells/patches-bash2. This will not > ^^^^^^^^ >Do you really need this ``patches-'' prefix here? This way you >spell out ``[Pp]atches'' twice in a path. Yeah, that does seem a little dumb, now that you mention it. >Thanks for doing this. Keep up a good work. Well, I'm just trying to see what ideas I can come up with. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu