wpkg --print-architecture
Short Hand
wpkg -c
| Options | Comments |
|---|---|
| --admindir | Define the administration directory, where the database of the installed packages resides. |
| --debug | Define a set of flags of things to print out for debug purposes. |
| --instdir | Define the installation directory, where the data files are installed on the target. |
| --quiet | Request for warning messages to not be displayed. |
| --root | Define the installation root path. |
| --verbose | Display log information of level INFO. |
The --print-architecture command reads the architecture of a target administration directory and prints it to stdout.
Since 0.9.0, wpkg supports all the architectures that Debian supports plus MS-Windows as an extension to the Debian list of architectures. Please see Architectures supported by wpkg for additional information about architectures in wpkg.
Note that wpkg checks the validity of the architecture information when you create a package, although it does not attempt to correlate the architecture specification with files being added to your package.
NOTE
Internally the architecture of a target is saved in a virtual package named core.
At this point wpkg does not support installations using multiple architectures. This can be palliated by the fact that you can create multiple environments on the same computer. For example, under MS-Windows 64 bit you can create two directories: target32 and target64. Then install your win32 packages under target32, and your win64 packages under target64.
Furthermore, assuming that you only plan to install distinct 32 and 64 bit packages, you could even make use of the --instdir option to install the package files under the same tree, but different --admindir so each installation has a distinct architecture.
wppkg --admindir admin32 --instdir target package_1.0_win32-i386.deb wppkg --admindir admin64 --instdir target package_1.0_win64-amd64.deb
