upe — Main module for all UPE operations

upe.build – Creating packages

Create packages from source.

Binary packages

Actually, creating packages from binaries is possible, but it shouldn’t be done because:

• It’s not practic: You have to create a package (or at least a build script) for each architecture you want to support.
• It’s not GNU style

But you may want to do it when:

• You are packing a very large package (Firefox, LibreOffice...) (see Gentoo’s Portage and Arch Linux’s AUR).

  Note

  In this case, package’s manifest must be (for Firefox, in this case):

  # Code showing only relevant parts
  package: firefox-bin
  pkgname: Firefox (binary)
  # ...
  tags:
    # ...
    binary: true
  

• You are packaging a privative or commercial software.

  Warning

  Remember that you

  • Can’t redistribute privative software without the original developer’s permission.
  • Shouldn’t distribute commercial software freely (again, without the original developer’s permission) (meaning, to people who hasn’t paid for it to the original developer).

  Note

  On UPE, commercial is applied to any application that requires the user to pay a license.

upe.config – Check UPE config

Check the config file. Further info in upe.config

upe.pkgmgmt – Install, remove and update packages

Use this module to do the basic operations: Install and remove.

Note

UPE will automatically upgrade a package when installing a newer version.