I have one small problem with your proposal, it only lets us make 2 debs from one build. I am going to put my proposal in an example:
Package: mystuff Version: 1.2.3 Revision: 1 Source: http://www.example.com/mystuff.tar.gz Debs: shlibs, docs, bin DebShlibs: %i/lib/libmylib-1.2.3.dylib %i/lib/libmystuff-1.2.3. DebDocs: %i/share/mystuff/* DebBin: %i/bin/* BinDepends: %n-shlibs (= %v-%r) BinDocFiles: README BinRecommends: %n-docs (= %v-%r) ShlibsDocFiles: README ShlibsRecommends: %n-bin (= %v-%r), %n-docs (= %v-%r) DocsDocFiles: README DocsRecommends: %n-bin (= %v-%r), %n-shlibs (=%v-%r) Depends: myotherstuff-shlibs BuildDepends: myotherstuff Recommends: %n-bin (= %v-%r), %n-docs (= %v-%r) DocFiles: README Homepage: http://www.example.com Maintainer: Me Myself <[EMAIL PROTECTED]> This example would make 4 debs: mystuff, mystuff-shlibs, mystuff-bin, mystuff-docs In your proposal there is no way to make more than 2 debs from a single build.. This is not so good. For example with db, I might want to make: db, db-cxx-shlibs, db-shlibs, db-bin, db-java, db-doc, db-tcl Well, I probably won't do this, but you see my point I hope. :) The info files are indeed getting messy, but I think the current format is more than up to the job of doing this. Peter On Thursday, February 14, 2002, at 12:49 AM, David R. Morrison wrote: > > 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. _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
