Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • apk-tools apk-tools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 108
    • Issues 108
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpine
  • apk-toolsapk-tools
  • Issues
  • #10680

Closed
Open
Created Mar 30, 2020 by Rasmus Thomsen@Cogitri

A higher level API for libapk

Hello,

I think it would be nice if libapk used a friendlier, higher level API for dealing with package operations, so that projects like QtApk or apk-polkit don't have to wrap as much functionality.

Overall, I think the following functionality should be exposed via a higher level API:

  • Add packages
  • Delete packages
  • Upgrading packages
  • Querying information about a package
  • Listing packages (and filtering, e.g. upgradable/installed)
  • Open/Close the database

Other bits probably aren't too interesting for projects using libapk.

Assignee
Assign to
Time tracking