[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

.deb package from compiled libraries



Hi

I was able to build a good .deb package of a library . thanks

I am not suer if you would like my following questions but there is a 
reason for them:

1. Is it possible to run pbuilder not in a chroot environment  without 
using base.tgz , But from  a local file tree ?
    I tried : pbuilder --debuid or pbuilder  --use-pdebuild-internal  but 
both use the base.tgz file.

2) I was watching the output of the dh_command s that come out as the 
rules/ binary-arch: target   run  (pbuilder).
    It seems it is possible to build a .deb package from an existing tree 
of binaries/libraries  that were pre compiled.
    What is the naming convention of  such a tree  path ? is it defined in 
the debian-policy ?

   - Can dpkg-shlibdeps accept several libraries in one call ( not clean 
from the man pages) ?
   - is the generation of  the postinst and postrm scripts mandatory ?

   - The  pbuilder run output shows dpkg-deb is  generating the final .deb 
file .
      What is the role of dpkg-buildpackage command (if any) that I do not 
see called explicitly ?

thanks

Zvi Dubitzky 
Email:dubi@il.ibm.com
IBM Haifa Research Laboratory    Phone: +972-4-8296182
Haifa, 31905, ISRAEL 



Reply to: