RE: non-blocking dependencies

> IMHO if a package that depends on another one can be used without,
> it
> should be considered to introduce corresponding option to the
> package.

I'd be happy with that, as long as there is an accompanying general guideline that dependencies that often fall into this category get extra review when packages are imported.  In this case, it should always be asked, "Is doxygen required just for the doco? If so, wrap it in an option."  Bulk builds on platforms where it's known to be broken (i.e. Solaris) could have that option globally disabled. The would alleviate most of the problems.  

> But in that particular case I'd go with fixing the doxygen.

That, of course, would be best.  It's more bandwidth than I can commit right now though.  If "solaris-pkg-people" wants to contact me off-list, I'd be happy to help remedy a few of the biggest (for me) problem packages. 


Tim

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev