4,144
edits
Changes
From Amahi Wiki
Package naming conventions (view source)
Revision as of 03:57, 17 October 2011
, 03:57, 17 October 2011Created page with "When specifying a package, this package has to be supported in all the distros supported in Amahi. Amahi now supports several ways to specify package names and package dependenc..."
When specifying a package, this package has to be supported in all the distros supported in Amahi.
Amahi now supports several ways to specify package names and package dependency names:
* When a package name is common to all systems, the name is simply how it's specified
* When a package name is specific to an rpm-based distro, it should be specified with:
rpm(package1 package2 package3 ... etc)
* When a package name is specific to a deb-based distro, it should be specified with:
deb(package1 package2 package3 ... etc)
So, for an app that supports both rpms and debs, and has common package names, the package or package dependency fields would look like this:
pkg0 pkg1 rpm(pkg3 pkg4) deb(pkg5 pkg6)
Amahi now supports several ways to specify package names and package dependency names:
* When a package name is common to all systems, the name is simply how it's specified
* When a package name is specific to an rpm-based distro, it should be specified with:
rpm(package1 package2 package3 ... etc)
* When a package name is specific to a deb-based distro, it should be specified with:
deb(package1 package2 package3 ... etc)
So, for an app that supports both rpms and debs, and has common package names, the package or package dependency fields would look like this:
pkg0 pkg1 rpm(pkg3 pkg4) deb(pkg5 pkg6)
