2.7.7

What's Changed

• Add annotation storage when creating a new package. by @laffer1 in #114
• Implement acl limiting with age restriction logic by @laffer1 in #115

Full Changelog: 2.7.6...2.7.7

2.7.6

Full Changelog: 2.7.5...2.7.6

2.7.5

Added new annotate command which allows you to add custom annotations to packages. This also introduces some new metadata about the OS the package was built on. (versions)

You can see the annotations with the mport info command or individual ones with mport annotate -S flavor

For FreeBSD pkg compatibility, we support flavor and cpe on the mport annotate -S commands but they aren't implemented as annotations.

add prelimiary support for -M flag (ingore missing dependenices) for mport install command

mport install -y now works. This is equivalent to setting the ALWAYS_ASSUME_YES env var to avoid nag questions when installing.

There are also quite a few memory safety bugs fixed in this release. This will impact mport upgrade, mport update and mport install paths as well as settings

Full Changelog: 2.7.4...2.7.5

2.7.4

Fixes bugs in sample file creation, a memory leak, error handling output, and a crash bug with mport upgrade

Full Changelog: 2.7.3...2.7.4

2.7.3

Improves handling of color on the terminal

Fix some bugs with the mport add command, which resulted in segmentation faults.

2.7.2

What's Changed

• Migrate rc.d start/stop to posix_spawn rather than using system by @laffer1 in #98

Full Changelog: 2.7.1...2.7.2

2.7.1

Added new functionality to mport verify:

• You can check a single port now with mport verify
• You can repair checksums now on a port. mport verify -r This often indicates a security issue, modified files after installation by the user, or a problem with mport package manager where an install was damaged.
• Fixed build issues with newer LLVM versions.
• Change the behavior of mport_install to include dependencies. make a new function mport_install_single to keep the old behavior for users. switch upgrade over to it.
• Attempt to detect packages that have the same origin for upgrades.

The last one needs more refinement in future releases. When you do mport list updates now, it may show you updates are available but if you run mport update it will fail for some. The reason is that it now figures out that we don't have a package for say py37-foo when there is for py311-foo. So it will suggest an update. It's not yet updating the package in this scenario. I need to rework some things for this to happen. My first implementation was reverted because of some other complications. Ideally, a user will need to be prompted to do this. There are cases it's wrong. (like if a packge was just not built on the last package build in magus)

I've also improved a lot of messages to the user, usage() output, and added more error handling in several places. There were a few small memory leaks fixed as well.

2.7.0

What's Changed

• Add preliminary lua script support by @laffer1 in #95
• load the linux kernel module before running ldconfig on linux emulation packages
• switch to posix spawn for running mtree
• /usr/libexec/mport.info now has an x flag that only prints pkgname-pkgversion
• fix the removal of the automatic flag when updating packages
• add automatic flag for mport.install
• add explit thread count to xz.
• Rework temp file creation to honor the TMPDIR env var
• Fix installation of info files (they weren't getting extracted when using @info annotation)
• Fix run of indexinfo when installing info files to use the directory
• Support cpe or purl commands for a single package. mport cpe gmake or mport purl gmake
• Support checking install paths on install media. (/packages)
• Make changes to pkg-plist parsing to be more portable.

Full Changelog: 2.6.8...2.7.0

2.6.8

What's Changed

• zstd compressed index files. by @laffer1 in #92
• add hash verification for index files. (external .… by @laffer1 in #93

Full Changelog: 2.6.7...2.6.8

2.6.7

Use https for index fetching

(2.6.6 was skipped due to a bug in audit)