| Age | Commit message (Collapse) | Author |
|---|
|
should be better.
|
|
finish the manual1 test
|
|
|
|
|
|
exemplify anything interesting now.
zap it from the list until it gets properly fixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to another without minor being bumped and a package depending on it needs to
be updated, like what happened in the thunar-vfs-1 @lib split from
thunar-1.0.x to thunar-vfs 1.2.x package.
|
|
containing entries becomes a real directory with the same entries, like in
the upcoming exo-0.6.0 -> exo-0.6.1 update.
|
|
more bogus packages so that we can get errors out of pkg_add...
|
|
also, PKG_ADD -> ADD_PKG to avoid confusion with bsd.port.mk.
|
|
|
|
|
|
|
|
|
|
occur (and thus we shouldn't downgrade packages if the version changes)
|
|
|
|
|
|
|
|
|
|
new test for signature comparison checks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
they should install/uninstall in the correct order to be able to handle any
@exec activity...
|
|
|
|
|
|
|
|
|
|
|
|
When a file moves between packages, one new package will conflict with
two old packages, in which case pkg_add should update both (and it does not,
not yet).
We distinguish from the case where a new package is an update for two packages
by the absence of a @pkgpath annotation.
|
|
|
|
|
|
|
|
|
