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:
> ...
>>> I am considering volunteering to be BRL-CAD package manager for Debian
> ...
>>> for my Debian-using clients, so that I would probably want to
>>> coordinate some changes with Jordi if I do become a Debian packager
>>> (such as possibly having a separate deb dir for Debian).
> ...
>> 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?

A lot of work, but mandatory to include brlcad into Debian repositories, not my 
decision but the Debian members.
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.

> 
>> I'm curious to knowing the changes you made on deb building process.
> 
> My changes (for a special project with some hacky customization):
> 
> 1. Currently I modify the system to install BRL-CAD in a versioned
> directory.  But I'm going to change back to the standard,
> non-versioned method you use (per Debian policy).
> 
> 2. I install a version file as "/etc/brlcad/version" with contents like:
> 
> 7.22.0

I'll include in the next release (deb & rpm)

> 
> 3. in script postinst I drive ld.so.conf as the final step:
> 
> # we need ldconfig
> ldconfig &>/dev/null || :
> 
> 4. In file "/etc/profile.d/brlcad.sh" I check for non-zero-length
> PATH and MANPATH before using them:
> 
> TPATH=/usr/brlcad/bin
> TMANPATH=/usr/brlcad/share/man
> 
> if [ -z "$PATH" ] ; then
>   PATH=$TPATH
> else
>   PATH=${PATH}:${TPATH}:
> fi
> if [ -z "$MANPATH" ] ; then
>   MANPATH=${TMANPATH}
> else
>   MANPATH=${MANPATH}:${TMANPATH}
> fi
> 
> export PATH
> export MANPATH
> 
> 
> I did that because I've had trouble before with Ubuntu if an env var
> is empty.  I can't say for Debian distros, but I'm still assuming the
> above is better practice.

Agree. To avoid any possible error I'll upgrade this script (deb & rpm)

> 
> 5. I added file "/etc/ld.so.conf.d/brlcad.conf" with contents like:
> 
> /usr/brlcad/rel-7.22.0/lib

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.

To avoid these kind of problems I've removed the control file "shlibs" for 
futures releases http://man.he.net/man5/deb-shlibs

> 
>> Anyway, I think that any improve/change applied to deb packages must be
>> applied to rpm too. Their differences are smaller that they seems.
> 
> Agree.
> 
> In summary, I plan to remove most  of my changes as I (1) use the
> Debian base file location for installation and (2) remove my localized
> hacks into their own deb.
> 
> So the only remaining differences with Jordi's version are the two
> additional control files and the PATH and MANPATH zero-length checks
> in "brlcad.sh".
> 
> Comments on remaining differences? I'm probably missing something
> standardly done with Debian (trying  to determine best packaging
> practices has been tough for me).
> 


-- 
Jordi Sayol

------------------------------------------------------------------------------
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

Reply via email to