Am 09.01.2019 um 13:27 schrieb Mathieu Arnold:
> CONFLICTS, CONFLICTS_BUILD and CONFLICTS_INSTALL exist to tell the user
> building the port that the port they are trying to install cannot be
> built-or-installed/build/installed while this other port is installed.
thanks for clarification, I
On Tue, Jan 08, 2019 at 11:48:42PM +0100, Matthias Fechner wrote:
> Hi Franco,
>
> Am 08.01.2019 um 15:58 schrieb Franco Fichtner:
> > Explicit CONFLICTS only exist within the ports tree
> > during builds.
> >
> > pkg detects conflicts simply when files are attempted
> > to be installed in the
Hi Franco,
Am 08.01.2019 um 15:58 schrieb Franco Fichtner:
> 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.
hm, this
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
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
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
