What about going The OMPI Way? :-) That is, having support for these things via dynamically loaded plugins. Since the plugins are loaded at runtime, the presence or absence of a plugin in the filesystem determines whether that output format is supported or not.
Hence, a hwloc-core package (RPM or deb or whatever) can contain the basic lstopo plugins, and a supplemental hwloc-x11 package (or whatever name they want) can contain the X11 based plugin. Ditto for Cairo. On Apr 25, 2012, at 8:13 AM, Chris Samuel wrote: > On Wednesday 25 April 2012 19:38:00 Brice Goglin wrote: > >> How do people feel about this? > > It sounds like what you have is a conflict between the policies of > Debian (and hence Ubuntu) and the expectations of RHEL/CentOS users. > > Debian Policy is fairly clear on this matter: > > # 11.8.1 Providing X support and package priorities > # > # Programs that can be configured with support for the X Window System > # must be configured to do so and must declare any package > # dependencies necessary to satisfy their runtime requirements when > # using the X Window System. [...] > > It says you can split it into a separate package to provide GUI > functionality *only* if the "package is of higher priority than the X > packages on which it depends" (which I suspect is not the usual case). > > cheers, > Chris > -- > Christopher Samuel - Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 > http://www.vlsci.unimelb.edu.au/ > _______________________________________________ > hwloc-devel mailing list > hwloc-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
