Difference between revisions of "Package naming conventions"

From Amahi Wiki
Jump to: navigation, search
Line 8: Line 8:
 
* When a package name is specific to a deb-based distro, it should be specified with:
 
* When a package name is specific to a deb-based distro, it should be specified with:
 
       deb(package1 package2 package3 ... etc)
 
       deb(package1 package2 package3 ... etc)
 +
* When a package name is specific to a single distro, e.g. u1010, it should be specified with:
 +
      u1010(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:
 
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)
 
       pkg0 pkg1 rpm(pkg3 pkg4) deb(pkg5 pkg6)

Revision as of 08:59, 17 October 2011

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)
  • When a package name is specific to a single distro, e.g. u1010, it should be specified with:
     u1010(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)