From pgj at freebsd.org  Tue Jan  2 06:57:27 2018
From: pgj at freebsd.org (Gabor Pali)
Date: Tue, 2 Jan 2018 07:57:27 +0100
Subject: [Freebsd-haskell] Porting haskell based software to FreeBSD
In-Reply-To: <4DBD41F9-0C6A-4BE0-8513-99A535F12164@FreeBSD.org>
References: <AA0871B8-6B5B-4FA2-B8D2-04B1EA6B0B9A@FreeBSD.org>
 <3d0b303a-168b-92e6-48ab-7ae6002ef2c6@FreeBSD.org>
 <CAHnG2CzYzUaQRWOGGZJffoLz_6Tu9SfGr7OamJzU+dZoar50Jw@mail.gmail.com>
 <5F9F9118-60D0-42D0-AA18-35A207413B76@FreeBSD.org>
 <CAHnG2CyQ-YbHbys9T_stctXahLU305=HGYbTC2jESmhdkQYhcg@mail.gmail.com>
 <4DBD41F9-0C6A-4BE0-8513-99A535F12164@FreeBSD.org>
Message-ID: <CAHnG2CzrUma4FDxeNSs=DiZQrX6s9kkb_Fbc=Caad92g3c0CJA@mail.gmail.com>

2018-01-01 13:28 GMT+01:00 Palle Girgensohn <girgen at freebsd.org>:
> The Q/A section of a poudriere build complains about secondary dependencies not being declared.

I have not worked with poudriere and the ports tree for a while now so
I cannot tell where the problem lies.  As far as I remember, you
should not have to declare any of the secondary dependencies in the
port.  If this is not false alarm then it should be taken care of by
the .mk files.  Although it is very interesting that you did not have
to include *all* the indirect dependencies, only vault for wai.

I would be curious of what more active committers, e.g. tcberner or
bdrewery think of this (find them CC'ed).

> ====> Running Q/A tests (stage-qa)
> Error: /usr/local/lib/cabal/ghc-8.0.2/x86_64-freebsd-ghc-8.0.2/libHSwai-middleware-static-0.8.1-L7ZRMO8gyE0B7dzzwf77cq-ghc8.0.2.so is linked to /usr/local/lib/cabal/ghc-8.0.2/x86_64-freebsd-ghc-8.0.2/libHSvault-0.3.0.7-7tuRxMAuJ018FM511jvs2K-ghc8.0.2.so from devel/hs-vault but it is not declared as a dependency
>
> Say like this:
>
> hs-wai-middleware-static/Makefile:
>
> USE_CABAL= wai
>
> hs-wai/Makefile:
>
> USE_CABAL= vault
>
> and when hs-wai-middleware-static is building (at least with poudriere) I get the error above, but the port still builds fine. Adding vault to hs-wai-middleware-static/Makefile removes the error, but it is against how ports usually work. Can I just ignore the errors?

It may happen that you will have to get away with adding vault
explicitly as a dependency as the package directly depends on it by
some build tool magic.