Hi Daniel! On 13 Sep 2005, at 19:45, Daniel Macks wrote:
On Tue, Sep 13, 2005 at 07:18:32PM +0200, Roland Kuhn wrote:On 13 Sep 2005, at 18:49, Alexander K. Hansen wrote:On 9/13/05, Daniel Macks <[EMAIL PROTECTED]> wrote:On Tue, Sep 13, 2005 at 06:33:56PM +0200, Roland Kuhn wrote:On 13 Sep 2005, at 18:19, Robert Jacobson wrote:I'd like to check out the package "khexedit". I see it on the Finkweb page, but I don't seem to have an info file for it.Other methods if you're offline include "fink dumpinfo -fparent <packagename>" --returns the parent package for a splitoff, and nothing for the parent package (or any other package that has no splifoffs) "fink dumpinfo -ffamily <packagename>? --returns all of the packagesin the .info file for <packagename>. The first one in this list is theparent package, which should usually be what the .info file is named for.As you say -fparent implies that one knows already that the package in question is not directly available (until it has been compiled, that is). So what about "fink find <package>", which scans the families and the children? I'd code it up if someone gave me a pointer where I should add this code...What's the real goal of the excercise here--I'm confused by your "directly available" comment. One doesn't need to know the parent in order to compile or install a package, nor does the parent even always need to be installed to install one of its children. But anyway, Alex is right: dumpinfo is the general way to find the internal details of a package ('fink dumpinfo -h' for help): -finfofile will tell you the .info filename and -ffamily always lists the parent first (whereas -fparent is blank if you ask about a parent package).
Okay, -finfofile does exactly what I was talking about. Maybe I was a bit unclear with "not directly available", I meant only querying, not building. But I also must correct myself: From the original posting and my (maybe incomplete) memory I thought that 'fink list khexedit' did not yield anything before installing (and thereby compiling) kdeutils3, which actually put the .deb into the local dists dir. But now I failed to re-create this behaviour...
Ciao, Roland -- TU Muenchen, Physik-Department E18, James-Franck-Str. 85747 Garching Telefon 089/289-12592; Telefax 089/289-12570 -- A mouse is a device used to point at the xterm you want to type in. Kim Alm on a.s.r. -----BEGIN GEEK CODE BLOCK----- Version: 3.12GS/CS/M/MU d-(++) s:+ a-> C+++ UL++++ P-(+) L+++ E(+) W+ !N K- w--- M + !V Y+
PGP++ t+(++) 5 R+ tv-- b+ DI++ e+++>++++ h---- y+++ ------END GEEK CODE BLOCK------
PGP.sig
Description: This is a digitally signed message part