Re: [MoM]: r9659 - trunk/packages/fis-gtm/fis-gtm/trunk/debian
On Mon, Feb 13, 2012 at 3:46 AM, Andreas Tille <firstname.lastname@example.org> wrote:
> Hi Luis,
> I became suspicious about your recent commit. At first I realised that
> you are using fixed version numbers in rules file. The idea should be
> to avoid touching debian/rules for new upsteam versions if possible.
> So I would probable use something like
> GTMVERSION=$(shell dpkg-parsechangelog | grep '^Version' | sed 's/Version: \([^-]\+\)-\([^-]\+\)-[0-9]\+$/\1\2/')
> instead of the fixed string V54002B.
> However, when thinking about this I wonder what the whole purpose of the
> copying and untaring of gtm_V54002B_linux_i586_pro.tar.gz might be. This
> tarball is not part of your upstream source tarball (the *.orig.tar.gz)
> and thus it's *not there* for the packaging process.
> Could you please be more verbose about your plan with this tar file?
This was my first lame attempt at
making progress on the installation front :-)
Here was my reasoning:
fis-gtm makefile provide a target called "package"
that takes the outcome of the build, and package it
into the tar file:
It contains a collection of executables, *.m files,
*.o files, and several scripts.
This is the same tar file that ones downloads
from sourceforge when manually installing
fis-gtm (as far as I understand...).
e.g. here are the instructions we use in that case:
So, my plan was:
1) Take advantage of the "package" target in the
gtm Makefile, to select the binary files of interest
to be included in an installation.
2) Take the resulting tar.gz file, expand it in a tmp
3) Finally, cherry-pick the files from that tmp
directory and put them in their final destination
Two alternative plans are;
A) To directly use the "./configure" file in the
binary directory, which actually pick some
defaults and move files to their final location.
B) Work from the "gtminstall" script that Bhaskar
pointed out. In this case, we have to skip several
portions of the script, because it really starts with
downloading the tar files from sourceforge.
This is clearly another chapter
in which I have a lot to learn... :-)
> Kind regards
> ----- Forwarded message from Luis Ibanez <email@example.com> -----
> Date: Sun, 12 Feb 2012 21:48:03 +0000
> From: Luis Ibanez <firstname.lastname@example.org>
> To: email@example.com
> Subject: r9659 - trunk/packages/fis-gtm/fis-gtm/trunk/debian
> Author: luisibanez-guest
> Date: 2012-02-12 21:48:02 +0000 (Sun, 12 Feb 2012)
> New Revision: 9659
> Now using the debian/tmp directory as intermediate
> step during the installation of the binaries.
> Modified: trunk/packages/fis-gtm/fis-gtm/trunk/debian/rules
> --- trunk/packages/fis-gtm/fis-gtm/trunk/debian/rules 2012-02-12 20:48:34 UTC (rev 9658)
> +++ trunk/packages/fis-gtm/fis-gtm/trunk/debian/rules 2012-02-12 21:48:02 UTC (rev 9659)
> @@ -25,8 +25,9 @@
> tcsh ./$(SRC_EXTRAS_DIR)/setupenv.sh package
> - cp ./gtm_V54002B_linux_i586_pro.tar.gz $(CURDIR)/debian/$(PKG)/usr
> - cd $(CURDIR)/debian/$(PKG)/usr
> + mkdir $(CURDIR)/debian/tmp
> + cp ./gtm_V54002B_linux_i586_pro.tar.gz $(CURDIR)/debian/tmp
> + cd $(CURDIR)/debian/tmp
> tar xzf ./gtm_V54002B_linux_i586_pro.tar.gz
> debian-med-commit mailing list
> ----- End forwarded message -----
> To UNSUBSCRIBE, email to debian-med-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
> Archive: 20120213084639.GC24744@an3as.eu">http://lists.debian.org/20120213084639.GC24744@an3as.eu