My first novice thought for package name was to split brlcad into several Debian binary packages similar to libxml2:
libbrlcad libbrlcad-dev libbrlcad-utils libbrlcad-doc libbrlcad-dbg with the source package retaining the name as is produced by the BRL-CAD dev team. However, after being pointed to this document I have some doubts about those choices: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#naminglibpkg So how about this for a start for consideration: brlcad <= libs + bin and other progs + man and html docs + headers (maybe gets so naming) brlcad-pdfdocs <= add full pdf docs I'm not sure so naming needs to be on the package name (but it could be). I don't think a deb user would be interested in using multiple versions. Note that with the Debian system a src package will also be available. Ideas appreciated. Best, -Tom ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
