On Tue, Apr 20, 2004 at 04:25:37PM +0300, Antti Tapaninen wrote:
> On Mon, 19 Apr 2004, Daniel Macks wrote:
> >
> > fink dumpinfo --source > output.txt
> >
> > (or something like that...the exact syntax isn't quite set yet) and
> > then you can browse a giant listing of all packages (or optionally
> > limitted by package name) and their macro-expanded tarball names at
> > your leisure. Would that provide the kind of info you want?
>
> Probably, but then I would have to make two separate tools, one for
> standard debian and other for Fink. :)
Wait, I think I answered the wrong question ("source" meaning the
tarball of .c files, not the parent package name).
> I still don't understand why Fink needs to keep both Source and Package
> fields in the final .deb file information identical, I managed to modify
> fink packaging routines so that it'll generate the packages into same form
> as Debian does. This way I can easily determine for my owns statistics the
> original source and version, of which the package(s) have been generated.
>
> Here's the change that I made:
>
> --- /sw/lib/perl5/Fink/PkgVersion.pm.orig Tue Apr 20 15:52:37 2004
> +++ /sw/lib/perl5/Fink/PkgVersion.pm Tue Apr 20 16:09:47 2004
> @@ -1722,7 +1722,7 @@
> $instsize = $self->get_instsize("$destdir$basepath");
> $control = <<EOF;
> Package: $pkgname
> -Source: $pkgname
> +Source: $self->{_expand}->{N}
> Version: $version
> Section: $section
> Installed-Size: $instsize
That indeed does look s like a bug. Appears to be unchanged when
SplitOffs (child packages) got implemented.
At least for fink, is the kind of thing you want?
% fink showparent gle3-shlibs
gle3-shlibs's parent is gle3.
% fink showparent gle3
gle3 is the parent.
% fink splitoffs gle3
gle3 has 1 child:
-> gle3-shlibs
% fink splitoffs gle3-shlibs
gle3-shlibs is a child, it's parent gle3 has 1 child:
-> gle3-shlibs
It's in fink now, but is completely undocumented.
> The tool that I started working on yesterday is at
> http://www.hut.fi/~aet/dpkg-glue. If anyone knows the correct spell that
> does about the same with standard dpkg/apt tools, please let me know. :)
The dpkg-* tools are the usual way to construct and manipulate .deb
archives and the various databasefiles. Have you looked at dpkg-query,
dpkg-scanpackages, and dpkg-deb? OTOH, it may be more efficient to
just read the files themselves as you are doing now.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
