On Fri, Apr 5, 2013 at 7:38 AM, Jordi Sayol <[email protected]> wrote: > On 05/04/13 13:23, Tom Browder wrote: >> On Wed, Mar 27, 2013 at 10:51 AM, Jordi Sayol <[email protected]> wrote: >>> On 22/03/13 19:52, Tom Browder wrote: ... >>> There are at least three basic things to make brlcad deb to accomplish with >>> Debian rules: >>> - split into multiple deb packages >> How do you see that split?
I wasn't very clear, Jordi. I meant to ask is that something like: two debs per lib (lib and lib-dev) # over 40 unique libs => 80+ deb packages And are the bin files their own deb? > A lot of work, but mandatory to include brlcad into Debian repositories, > not my decision but the Debian members. Can you point to the Debian document discussing that part? > This is not the first step to be taken. Before that, make all brlcad tools > properly > work on /usr instead /usr/brlcad, and use system shared libraries. Okay. >> 3. in script postinst I drive ld.so.conf as the final step: ... >> 5. I added file "/etc/ld.so.conf.d/brlcad.conf" with contents like: ... > About point 3 and 5, I'm not sure that is good to share system wide > the /usr/brlcad/lib shared libraries. This will raise more problems than > solutions I think. So how do you handle the user finding brlcad libs? LD_LIBRARY_PATH is not good practice as I understand it these days--I thought using ld.so.conf.d was the thing to do. Best regards, -Tom ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
