Re: [MoM] Packaging fis-get
On Tue, Feb 07, 2012 at 11:14:47AM -0500, Luis Ibanez wrote:
> In the mumps-clean machine,
> I had to install the following
> dependency packages:
>
> apt-get install libicu-dev
> apt-get install gnupg-doc
> apt-get install tcsh
> apt-get install zlib1g-dev
> apt-get install libncurses-dev
> apt-get install libgcrypt11-dev
So you should mention all thses as "Build-Depends" in the debian/control
file.
> Type:
>
> ./setupenv.sh
This translates into the debian/rules file as
override_dh_auto_conf:
./setupenv.sh
> This initiates the build, and seems
> to proceed to the end without errors.
>
> It turned out that we don't need the *.d files in the set
> of new sources, so they were removed from the branch.
Great - the less extra files the better.
> Here is below the "diff" between the master branch
> (the original fis-gtm code), and the "configured" branch,
> where we put the generated code.
>
>
> .gitignore | 6 +
> fake-binary-surrogates/mumps | 2 +
> pro/gtm_limits.h | 64 +
> pro/gtm_stdio.h | 137 ++
> pro/gtm_stdlib.h | 50 +
> pro/gtm_string.h | 32 +
> pro/gtm_strings.h | 20 +
> pro/gtmxc_types.h | 87 ++
> pro/main_pragma.h | 21 +
> pro/obj/cmerrors_ctl.c | 35 +
> pro/obj/cmierrors_ctl.c | 73 +
> pro/obj/gdeerrors_ctl.c | 135 ++
> pro/obj/gtm_threadgbl_deftypes.h | 442 ++++++
> pro/obj/merrors_ansi.h | 1226 +++++++++++++++
> pro/obj/merrors_ctl.c | 2447 ++++++++++++++++++++++++++++++
> pro/obj/omi_sx_play.c | 488 ++++++
> pro/obj/ttt.c | 664 ++++++++
> pro/plugin/gtmcrypt/gtmcrypt_dbk_ref.c | 419 +++++
> pro/plugin/gtmcrypt/gtmcrypt_dbk_ref.h | 117 ++
> pro/plugin/gtmcrypt/gtmcrypt_interface.h | 24 +
> pro/plugin/gtmcrypt/gtmcrypt_pk_ref.c | 382 +++++
> pro/plugin/gtmcrypt/gtmcrypt_pk_ref.h | 115 ++
> pro/plugin/gtmcrypt/gtmcrypt_ref.c | 251 +++
> pro/plugin/gtmcrypt/gtmcrypt_ref.h | 245 +++
> pro/plugin/gtmcrypt/gtmcrypt_sym_ref.h | 174 +++
> pro/plugin/gtmcrypt/gtmxc_types.h | 87 ++
> pro/plugin/gtmcrypt/main_pragma.h | 21 +
> pro/plugin/gtmcrypt/maskpass.c | 123 ++
> pro/utf8/gtm_limits.h | 1 +
> pro/utf8/gtm_stdio.h | 1 +
> pro/utf8/gtm_stdlib.h | 1 +
> pro/utf8/gtm_string.h | 1 +
> pro/utf8/gtm_strings.h | 1 +
> pro/utf8/gtmxc_types.h | 1 +
> pro/utf8/main_pragma.h | 1 +
> setupenv.sh | 47 +
> sr_linux/gtm_threadgbl_deftypes.h | 442 ++++++
> 37 files changed, 8383 insertions(+), 0 deletions(-)
>
>
>
> I have now to attempt installation,
> and go through the process of
> verifying if that installation is fully
> functional.
If there is some install script provided by fis-gtm you should do
something which looks like
PKG := $(shell dpkg-parsechangelog | sed -n 's/^Source: //p')
override_dh_auto_install:
<fis_gtm_install_script> PREFIX=$(CURDIR)/debian/$(PKG)/usr
or something like this if fis-gtm knows such PREFIX variable.
Alternatively you can install to
$(CURDIR)/debian/tmp
and use dh_install afterwards to move files around. There are zillions
of examples in Debian Med SVN. Just have a read in some of the
packaging examples there and watch out for debian/rules and
debian/install files.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: