Top Menu

Jump to content
  • Package manager
    • View all projects
Home
    • Work packages
    • News
    • Getting started
    • Introduction video
    • Welcome to OpenProject

      Get an overview

      Get a quick overview of project management and team collaboration with OpenProject.
      You can restart this video from the help menu

    • Help and support
    • Upgrade to Enterprise Edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Create a new account
      Forgot your password?

Side Menu

  • Overview
  • Activity
  • Work packages
  • News
  • Forums
  • Repository
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leafCaches and Metadata locations
        • Hierarchy leafConfiguring pkgmanager
        • Hierarchy leafHelp
        • Hierarchy leafInstalling new software
        • Expanded. Click to collapseCollapsed. Click to showPackaging new software
          • Hierarchy leafPackage structure and metadata
          • Hierarchy leaftxz format
        • Hierarchy leafRemoving software
        • Hierarchy leafUpgrading software
You are here:
  • Wiki
  • Packaging new software

Content

Packaging new software

  • More
    • Table of contents

pkgmanager makepkg arguments explained

pkmanager creates a package from the current directory by being executed like shown in the example below:

pkgmanager --makepkg --pkgname example --version 3.0.1 --arch x86_64 --build_tag repo --build_number  1


# --makepkg switches the pkgmanager to the makepkg mode

# pkgname is the name of the package

# version can be given without any symbol restriction, but be aware of going
# far away from the numbers-and-dots ideology since this field is used to calculate which package with 
# different version and same name should be threatet as a more actual one.

# Arch field is a field to represent the arch the package is built for.

# Build tag is a common sense fieled mostly used to separate the packages belonginess to repositories used in the system.

# Build number represents number of rebuilts done in pipeline. Newer builds upgrade older builds if versions are same.

If we want to build a package not from the current directory we can change the behavior with "--build_folder" argument. It should point to the directory which is the root of the files to be packaged.

Example of how a piece of software can be packaged

# build and install the software to a fake root
cd awesome-programm-1.0
./configure; make; make install DESTDIR=$PKG

# This will create a new package in /build directory
pkgamanager --makepkg --pkgname awesome-programm --version 1.0 --arch x86_64 --build_number 1 --build_tag dev --build_folder $PKG

# build_folder is set by default to 
cd $PKG
pkgamanager --makepkg --pkgname awesome-programm --version 1.0 --arch x86_64 --build_number 1 --build_tag dev
Loading...