There are now 15 packages which have been converted to the new style of pkg and pkg-shlibs; I thank all of you for your contributions to this project.
The next step in the project is to develop a system by which both pkg and pkg-shlibs will be created from a single .info file (through an extension to fink). Max and I worked out a broad outline of this in a discussion here a few weeks ago. I have created model .info files (and .patch files) for all 15 of these packages, and put them in a new directory in CVS, /dists/shlibs. (This directory should be regarded as temporary, while we do testing and development of this extension to fink.) There is a README file which describes the format, which I reproduce here: The files in this directory are not currently valid fink .info files, but rather examples intended for testing an extension of fink under development. The extension involves a new type of fink package, Type: shlibs. A number of the standard fink .info items get shlibs variants, including: ShlibsDocFiles ShlibsDepends ShlibsConflicts and so on. The key extra .info item is a new one, Shlibs:, designating a list of files which ought to be put into pkg-shlibs rather than pkg. What fink is supposed to do with one of these descriptions (but doesn't yet do) is to generate two packages, pkg and pkg-shlibs. The compile and install phases will only be run once, but then dpkg will be called two times to generate two packages. Shlibs: tells which files should be moved to pkg-shlibs, and ShlibsDocFiles provides for some other files to be added to that package via the DocFiles method. Other than that, the ShlibsDepends, and so on, would be used to specify those debian fields for the .deb file. Comments are welcome. -- Dave _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
