A Debian "package", or a Debian archive file, contains the executable files, libraries, and documentation associated with a particular suite of program or set of related programs. Normally, a Debian archive file has a filename that ends in .deb. The internals of this Debian binary packages format are described in the deb(5) manual page. This internal format is subject to change, therefore always use dpkg-deb(8) for manipulating .deb files.

Packages generally contain all of the files necessary to implement a set of related commands or features. There are two types of Debian packages: Binary packages, which contain executables, configuration files, man/info pages, copyright information, and other documentation. These packages are distributed in a Debian-specific archive format; they are usually distinguished by having a '.deb' file extension.

The Debian package names conform to the following convention: <foo>_<VersionNumber>-<DebianRevisionNumber>_<Arch>.deb Note that foo is supposed to be the package name. This naming convention is rather new, and some packages have slightly different name formats. As a check, one can learn the package name associated with a particular Debian archive file (.

Unfortunately, I am not a Debian user so I cannot personally provide a package for Debian use. However, Roberto Sanchez has provided a Debian package for ReleaseForge.

No, on both counts, although there are various preprocessor tricks you can try (see the links below). You can convert base-2 string representations to integers with strtol. If you need to print numbers out in base 2, see the example code in question 20.10.

The Debian binary package file names conform to the following convention: <foo>_<VersionNumber>-<DebianRevisionNumber>.deb Note that foo is supposed to be the package name. As a check, one can learn the package name associated with a particular Debian archive file (.deb file) in one of these ways: inspect the "Packages" file in the directory where it was stored in a Debian FTP archive site.

Debian created by the Debian project, is a widely used distribution of free software developed through the collaboration of volounteers from around the world.

The version for a non-native Debian package looks like UpstreamVersion-DebianVersion for example: 2.8-1. In the diff.gz: These are the modifications you made to the package. It contains the debian directory and the modifications you made to the source tree, if any. In the orig.tar.gz: This is the upstream tarball. You should very rarely make changes to this file, and you should never ever make changes unless you explicitly understand why you are making them.

You need to convert your data to the HTK parameter format (you can eiter use the USER parameter kind or pretend they are MFCC or similar). Typically this involves writing a small programm that does the conversion. For an example see HTKWrite.c This happens if you try to compile HTK 3.3 using GCC version 4. You can find details about how to fix this here. Note that this has been fixed in 3.4 and we strongly recommend that you upgrade to the latest release.

You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile the source (note: there is no .diff.gz for some packages that are native to Debian). Once you have them (How do I install a source package?, Section 7.13), if you have the dpkg-dev package installed, the following command: dpkg-source -x foo_version-revision.

The binary executables outputted by pp (on Linux) are not valid ELF binaries because it basically attaches a zip archive to the binary loader and does not modify the ELF headers to reflect that. When building an RPM archive, the validity of the ELF headers is checked by default. This can result in problems when packaging pp-ed binaries in RPM archives. I]t appears that the RPM archive that is generated gets a list of the MD5 sums for components of the executable file calculated by prelink.

Debian GNU/Linux is a particular distribution of the Linux operating system, and numerous packages that run on it. In principle, users could obtain the Linux kernel via the Internet or from elsewhere, and compile it themselves. They could then obtain source code for many applications in the same way, compile the programs, then install them into their systems. For complicated programs, this process can be not only time-consuming but error-prone.

This is stable and well tested software, it changes if major security or usability fixes are incorporated. This is where packages that will be released as the next 'stable' are placed; they've had some testing in unstable but they may not be completely fit for release yet. This distribution is updated more often than 'stable', but not more often than 'unstable'. This is the version currently under development; it is updated continuously.

You can get the installation disks by downloading the appropriate files from one of the Debian mirrors. The installation system files are separated in subdirectories of dists/stable/main directory, and the names of these subdirectories correspond to your architecture like this: disks-arch (arch is "i386", "sparc", etc, check the site for an exact list).