On 1/8/19 3:58 PM, Franco Fichtner wrote:
Hi Matthias,
Explicit CONFLICTS only exist within the ports tree
during builds.
pkg detects conflicts simply when files are attempted
to be installed in the same place -- i.e. a file already
belongs to another installed package.
Cheers,
Franco
On 8. Jan 2019, at 3:52 PM, Matthias Fechner <ide...@fechner.net> wrote:
Dear all,
I just implement some changes in the gitlab-ce port which requires some
conflicts.
I tried to add:
CONFLICTS_INSTALL= gitolite-* \
gitolite2-* \
gogs-* \
${PYTHON_PKGNAMEPREFIX}-gitosis-*
My test machine has gitolite and gitlab-ce installed.
If I know execute pkg upgrade it does not trigger the conflict.
I had expected that pkg forces now a deinstallation of gitolite before
it continues with upgrading gitlab-ce.
But it just installs gitlab-ce and ignores the conflict definition.
Is this a bug in pkg or is something with the definition of the conflict
not correct?
Thanks.
Gruß
Matthias
-- "Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
@Matthias pkg detect conflict in files and tries to solve it (sometimes)
by deinstalling
the packages that conflict with the one you are trying to install.
If I remember well, the deinstall is not forced, and you has to validate it.
Cheers
- rodrigo
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
