Thava Alagu wrote: > > As I understand dependency does not serve any purpose other than > usability -- for users > to easily discover dependencies and get the software up and running. > So, too obvious dependencies may be omitted. For example, a package > may not > specify (directly or indirectly) the dependency to libc.so. I think it
Not really, take a look at the default depend file which includes all the basics. At the end of the day, most importantely, consider the end user! If you provide component foo, I (as a user) want to be able to take a freshly installed OpenSolaris 2008.05 instance and type % pkg install foo and once that's done, foo needs to work. So foo needs to have dependencies to bring in anything else it needed. Of course there's still things that can't be expressed.. for example phpPgAdmin certainly needs a working Postgres installation somewhere for it to be useful , but that somewhere is often on some other machine, so there's no way to express that in the package dependency... But do make sure it covers anything needed on localhost at least. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
