Source: tp-na
Section: dsi
Priority: extra
Maintainer: Jose M Calhariz <jose.calhariz@ist.utl.pt>
Build-Depends: debhelper (>= 4.0.0)
Standards-Version: 3.6.1

Package: tp-na
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .
 This package is available on all archs, so you don't really needed
 it.
 .


Package: tp-na-i386
Architecture: i386
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available on i386
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .

Package: tp-na-amd64
Architecture: amd64
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available on amd64
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .

Package: tp-na-powerpc
Architecture: powerpc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available on powerpc
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .

Package: tp-na-alpha
Architecture: alpha
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available on alpha
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .

Package: tp-na-sparc
Architecture: sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available on sparc
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .

Package: tp-na-rpi
Architecture: armhf
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: represents a package or feature not available on raspberrypi
 Sometimes when declaring depends, it is necessary to depend on a
 package not available on all architectures.  If depend is really
 needed on supported archs but don't needed on the others
 architectures, then declare a depends on a package tp-na-<ARCH> for
 all architectures your package can work, but the depend is not
 available.
 .
 This kind of package is more useful for depends on meta-packages.
 .
