1. I believe there is a need to document how to build a Debian
package (particularly how to set build options and dependencies), but
should it be a separate document or part of the README or INSTALL
files?
Given there are veritably dozens of potential platforms one might build, each with their own options, I certainly wouldn't put any instructions into the top-level README/INSTALL files. They could go into the platform-specific README files (in doc/README.*) though.
2. The Debian packages for a release should include a 64-bit version.
In addition, I think there should be a release note documenting the
options the Debian binary packages were built with. Is a survey of
package users warranted?
3. I can provide a 64-bit binary package easily if needed, but
doesn't the BRL-CAD server have that capability? Is the package
generation done automatically?
It's not done automatically (yet). Getting continuous integration set up is something on the TODO list after unveiling the new website.
4. I am getting build errors for the package with version 7.20.2 and
am investigating, but is the package generation still being tested or
is it supposed to be stable?
Ditto prior comments. Maybe Jordi can comment specifically on Debian.
Cheers!
Sean
------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
