On Jul 25, 2013, at 09:01 AM, Tom Browder <tom.brow...@gmail.com> wrote:
My first novice thought for package name was to split brlcad into
several Debian binary packages similar to libxml2:
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
Sounds like as good a start as any to me.
Ideas appreciated.
I don't have much to offer here, other than to say that I have been thinking a lot lately about creating stand-alone sub-distributions of the pieces in BRL-CAD that stand very well on their own. These are the pieces of logic that could very easily be projects of their own had they been developed in any other context.
I probably start with libbu or bu+bn as a test case to shake out the issues. Some other ones that come to mind for near-term deployment include the benchmark suite, libpkg, libnmg, libg, and libgcv. I've updated some of the doc/PROJECTS file to reflect some of those descriptions.
Cheers!
Sean
------------------------------------------------------------------------------ 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