[Clam-devel] suggestion about INSTALL file

[Hernán Ordiales]

On 6/13/07, David García Garzón <dgarcia at iua.upf.edu> wrote:
> Well, that's once you have the clam debian package.

mmm, no, i mean for compiling
i use it inside every dir of clam source to check and install packages
if necessary
(after the execution, if you need some dependecies they are printed in
the console)

PATH = CLAM | NetworkEditor | Annotator | Voice2Midi | etc

if there are some missing:
PATH$ dpkg-checkbuilddeps
(list of dependencies)
PATH$

if it's all ok:
PATH$ dpkg-checkbuilddeps
PATH$

for example i made a little test here (for double-checking):
hordia at CasaUsher:~/dev/clam_dev/CLAM$ sudo apt-get remove portaudio19-dev
...
hordia at CasaUsher:~/dev/clam_dev/CLAM$ dpkg-checkbuilddeps
dpkg-checkbuilddeps: Unmet build dependencies: portaudio19-dev
hordia at CasaUsher:~/dev/clam_dev/CLAM$ sudo apt-get install portaudio19-dev
hordia at CasaUsher:~/dev/clam_dev/CLAM$ dpkg-checkbuilddeps
hordia at CasaUsher:~/dev/clam_dev/CLAM$

> The INSTALL file is
> intended for people compiling from scratch.

yes, i think is useful for compiling from scratch

> What you suggest still requires
> installing dpkg-dev on a first instance.

yes, true

> Maybe it is a matter of taste, but i
> prefer keep the build process independent from the packaging.

yep, but in the same way you are enumerating dependencies for ubuntu
feisty/edgy or fedora core i think you can also suggest it for any
debian based distro

cheers,
-- 
Hernán
http://h.ordia.com.ar
GnuPG: 0xEE8A3FE9