[Pkg-octave-devel] Bug#452529: Bug#452529: several new upstream versions available

[Mr Syed Azeezullah]

Hello all,

----- Original Message -----
From: Thomas Weber <thomas.weber.mail at gmail.com>
Date: Tuesday, November 27, 2007 6:39 am
Subject: Re: [Pkg-octave-devel] Bug#452529: Bug#452529: several	new
upstream versions available
> Am Montag, den 26.11.2007, 17:43 +0100 schrieb Ólafur Jens Sigurðsson:
> > Ok, here is my first try at making a package :-)
> 
> Cool. Finally someone who actually wants to spend some time on 
> packagingthis stuff. Welcome on board.

Yes, It is great to see someone finally doing some work towards
octave-forge packaging.

> > http://www.fys.ku.dk/~ojs/octave-statistics.tgz
> > 
> > In this is the .tar.gz file from octave-forge and the debian dir 
> that> the package is built in (I have issued dpkg-buildpackage -uc -
> us for
> > this dir as a normal user).
> 
> Your rules file needs some work. Your postinst/prerm approach is
> interesting; I hadn't thougt of that. 
> Do you have any preferred form of version control? That'd make
> collaboration easier.
> 
> 	Thomas

Ok, there is a `problem' I see with the package. Please do correct me if
my understanding or statements are wrong.

Using `octave --eval "pkg install blah.tar.gz"' is the wrong way to go
when installing octave-forge packages. End-users will need to have
_many_ -dev packages installed to build and install the octave-forge
package. While using octave's pkg is good enough when installing
packages with only .m files, it is not the appropriate way to install
packages have binary files created during install, OdePkg for example.

Regards,
Imran