Brock Pytlik wrote: > "known" implicit dependencies: > The first step would be to catch what I'll call #! dependencies. The > idea is to use the #! at the top of py and other similar files to catch > a dependency on python (for example) or ksh, etc. > > The goal is to make the framework pluggable so that it's simple to add > other dependency catchers to the program. Obvious (if not easy) ones I > can think of would be library dependencies from elf files, compression > dependencies, maybe java dependencies if that's possible, directory > dependencies (?), and probably lots more that I'm not thinking of at the > moment. The goal won't be to have all those ready for the first putback, > but to have a framework in place that makes adding them reasonably simple.
Having spent far too much time over the past years on a perl script to check SVR4 packages for dependencies (see [1]) I can suggest a few more as well, such as .h files that #include other .h files, man pages that use .so to display other man pages, pkg-config .pc files that list other .pc files as required, etc. However, once you have faceted packages, you'll also want these dependencies to only apply to specific facets, such as .h dependencies being used when you install the development facet but ignored if you don't. I know Bart's spent some time thinking about these - will your work tie into that as well? [1] http://mail.opensolaris.org/pipermail/pkg-discuss/2009-March/011865.html -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
