mport.h

Checkout Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
revert recursive query logic. does not play nice with libdispatch

  1. … 7 more files in changeset.
add additional flags for monitoring changes

add additional fields and bump both version fields

  1. … 4 more files in changeset.
fix package meta pointer

  1. … 2 more files in changeset.
fix header

Migrate the asset list routine to it's own file and include extra fields so it can be used elsewhere.

Introduce a new function to get a package metadata from a file path. This allows us to find out what installed a file.

  1. … 5 more files in changeset.
use a tailq rather than a select intermixed with inserts. this will limit possible issues since we are using the same connection to the db

  1. … 1 more file in changeset.
add asset dir owner mode type.

  1. … 2 more files in changeset.
start work on @(root,wheel,0755) command structure

  1. … 7 more files in changeset.
Create an mport_info public api

  1. … 2 more files in changeset.
add list functionality to index. We can now list everything in the index via public api

  1. … 2 more files in changeset.
add a new public api for fetching indexes explicitly

  1. … 1 more file in changeset.
add some libdispatch love

  1. … 9 more files in changeset.
add blocks support for future use in libmport

  1. … 1 more file in changeset.
add an initial statistics api

  1. … 2 more files in changeset.
bump the midnightbsd mport version after recent changes.

  1. … 1 more file in changeset.
Initial implementation of pre exec/unexec and post exec/unexec for plists

Historically we've run @exec and @unexec inline. While this is still supported, we're now refactoring to allow steps before

and after package runs.

@preexec and @postexec fire on install and updates

@preunexec and @postunexec fire on deletes. (and updates when removing)

  1. … 3 more files in changeset.
teach libmport about @shell. We want to take this a step farther and "register" the shell next.

  1. … 4 more files in changeset.
Add support for locking and unlocking packages to libmport. This will allow a user to block update or delete operations on packages

  1. … 8 more files in changeset.
add preliminary support for sample files aka @sample in the plist. This currently only installs the sample file, but eventually will do some additional steps.

  1. … 6 more files in changeset.
first pass at supporting permissions aka chmod, chown, chgrp as well as @dir command

  1. … 3 more files in changeset.
add CPE column to mport bundles and the master list. bump the MPORT database version to 3 as well as the bundle version

  1. … 5 more files in changeset.
make mport_get_osrelease a public api

  1. … 3 more files in changeset.
Start populating os_release. needs more work

  1. … 5 more files in changeset.
Introduce new functions:

mport_version() (public) to display bundle version and currently running os.

mport_get_osrelease() (private util) to get the os release from sysctl

Packate stubs now include the OS version the package was created for in the meta table as os_release key. This way, we know what OS version the package was built for. Fetching packages currently relies on a static define in the mport tool and this may go dynamic in the future.

It might be useful to install old packages in newer os versions in some scenarios such as jails.

Also, bump the fetch url to 0.5 for 0.5-CURRENT as we're starting to tinker with the package format. The idea is to assume packages are for old releases if they don't include the meta[os_release] and allow a new mechanism to upgrade all packages for those built on the current release when we do major updates.

  1. … 3 more files in changeset.
accept optional version parameter to mport_install. This allows users to remove ambiguity with ports like ruby or tcl.

  1. … 2 more files in changeset.
add missing definition for index depends.

move fetch bundle into the public header until we can clean up mport

  1. … 1 more file in changeset.
don't copy and paste things.. this happens

Introduce package verify feature. Goes through checksums mentioning those that fail.

  1. … 1 more file in changeset.