Just for those who might not read debian-devel.
Laszlo, many thanks for including it straight into the tasks file which
saves me some work! (I sometimes wished others would follow your
example.)
Kind regards
Andreas.
- Forwarded message from Laszlo Kajan lka...@rostlab.org -
On Mon, Feb 13, 2012 at 5:38 PM, Andreas Tille andr...@an3as.eu wrote:
On Mon, Feb 13, 2012 at 04:45:04PM -0500, Bhaskar, K.S wrote:
If gtm_version is set, it does not download anything. So, for
installing a GT.M binary that is built from source, Luis can simply
use the gtminstall script.
Hi Luis,
On Wed, Feb 15, 2012 at 08:20:14AM -0500, Luis Ibanez wrote:
Using the ./pro/gtminstall script was almost too easy:-)
Here is how the rules file looks like now:
override_dh_auto_install:
./pro/gtminstall --utf8 default --installdir $(CURDIR)/debian/tmp
Hmmm:
On Wed, Feb 15, 2012 at 9:28 AM, Andreas Tille andr...@an3as.eu wrote:
Hi Luis,
On Wed, Feb 15, 2012 at 08:20:14AM -0500, Luis Ibanez wrote:
Using the ./pro/gtminstall script was almost too easy :-)
Here is how the rules file looks like now:
override_dh_auto_install:
On Wed, Feb 15, 2012 at 9:43 AM, Luis Ibanez luis.iba...@kitware.com wrote:
On Wed, Feb 15, 2012 at 9:28 AM, Andreas Tille andr...@an3as.eu wrote:
Hi Luis,
On Wed, Feb 15, 2012 at 08:20:14AM -0500, Luis Ibanez wrote:
Using the ./pro/gtminstall script was almost too easy :-)
Here is how
On Wed, Feb 15, 2012 at 09:43:44AM -0500, Luis Ibanez wrote:
Did you get this message as a result
of running debuild ?
Actually pdebuild (because this ensures english error messages as a side
effect).
I was working on the assumption that debuild goes
through a sequence of
* configure
*
On Wed, Feb 15, 2012 at 10:03:35AM -0500, Luis Ibanez wrote:
More on this,
I just reran debuild (still using the -I- option),
to attempt to replicate the installation stage.
In my case, it find ./pro/gtminstall, just fine,
but it has trouble finding the configure file.
So,
something
On Wed, Feb 15, 2012 at 04:29:16PM +0100, Andreas Tille wrote:
As a last resort for the *initial* packaging it might work out. Once we
are doing the real packaging we should not try such dirty tricks.
Now that we can generate a mumps compiler by way of
compiling only C code I wonder whether
On Wed, Feb 15, 2012 at 11:49 AM, Karsten Hilbert
karsten.hilb...@gmx.net wrote:
On Wed, Feb 15, 2012 at 04:29:16PM +0100, Andreas Tille wrote:
As a last resort for the *initial* packaging it might work out. Once we
are doing the real packaging we should not try such dirty tricks.
Now that
On Wed, Feb 15, 2012 at 12:35:35PM -0500, Luis Ibanez wrote:
As a last resort for the *initial* packaging it might work out. Once we
are doing the real packaging we should not try such dirty tricks.
Now that we can generate a mumps compiler by way of
compiling only C code I wonder
On Wed, Feb 15, 2012 at 06:43:59PM +0100, Karsten Hilbert wrote:
I believe Andreas was using initial as in version 0.1
of the packaging, e.g. the first quick and dirty way of
getting it done, and then revising it to follow better
practices and cleaner methods to become a version 1.0.
On Wed, Feb 15, 2012 at 04:29:16PM +0100, Andreas Tille wrote:
The problem is that *my* fis-gtm_5.4-002B.orig.tar.gz tarball does not
contain the file fis-gtm-src-extras/pro/gtminstall. Should I recreate
the orig.tar.gz???
I recreated the tarball now and can confirm that this file is just
On Wed, Feb 15, 2012 at 09:45:51PM +0100, Andreas Tille wrote:
As far as I understood the resulting C files only work for a specific
version and not for an upgrade.
Regardless of whether that is actually the case - you are
right, this is quite possible. Even if it would simply be
that later
Hi Andreas,
Derby requirement should be gone. Hope that helps and let me know if you
run into any other issues.
Take care,
Stephen
On 01/31/2012 10:21 AM, Andreas Tille wrote:
Hi Stephen,
On Tue, Jan 31, 2012 at 09:52:32AM -0500, Stephen Smith wrote:
No problems. How about I just change it
14 matches
Mail list logo
