Re: standard pkg suggested options

On Fri, Nov 15, 2013 at 10:31:53PM +0100, Niclas Rosenvik wrote:
> Hi everyone on pkgsrc-wip-discuss.
> I wonder if there are any conventions, standards etc on build options
> that should be enabled as default?
> 
> The reason I am asking is that one package I am working on needs doxygen
> to generate it's documentation and man pages. Doxygen depends a lot of
> packages, so it will take a long time to install and I don't want to
> waste peoples time. The question is if the documentation should be
> included by default or not.

I think in the end it depends on the relative sizes and how necessary
the documentation is.

For example for the sizes: if gzip or some other small package would
depend on doxygen for its docs, I'd probably make a separate package
for it. However, if a kde package needed doxygen for its docs, I
wouldn't hesitate adding the dependency.

Some packages have a 'doc' option; then you can set the default to one
value, for example include it, but make it easy for users on slow
machines to turn it off.

All a matter of preference, in the end...
 Thomas

------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk