Control File: invalid dependency architecture

Submitted by Alexis Wilke on Fri, 03/22/2013 - 05:10

When specifying a dependency, you can define a pattern that has to match an architecture. This way, you can define different dependencies depending on the architecture you are creating the package for.

This can be useful because under an Ubuntu system you may assume that Gnome (Gtk+) is installed, whereas under MS-Windows, it is not likely. So under Linux you may not even put the dependency to the Gtk+ because you have others that imply it. Then under MS-Windows you may install Gtk+ to get that installed along your software.

If the architecture information is not valid then this error occurs. Note that any architecture not currently supported by wpkg is considered an error since the package could not be installed without wpkg (although... yes, it could possibly work with dpkg if available on those platforms! that's currently a limitation of wpkg. We may add other architectures names later with a flag to know whether the architecture is valid, but not supported.)

VALIDDepends: boost [linux-i386]
INVALIDDepends: boost [macintosh-ppc]