tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Writing buildlink files: optional dependencies?

When creating a for a package foo that exposes libfoo, if 
libfoo depends on libbar (from package bar), my understanding is that I 
should include ../../whatever/bar/ in foo's

But how do I handle the case where foo only depends on bar when built with 
the "bar" option? Do I consult If yes, how do I make sure 
that the newly created doesn't run out of sync with the file (of foo)? The next version of foo built with the "bar" 
option could depend on bar-ng.

Home | Main Index | Thread Index | Old Index