Bug 204291 - print/hs-hscolour: dependency loop with option HSCOLOUR
Summary: print/hs-hscolour: dependency loop with option HSCOLOUR
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-haskell mailing list
Keywords: needs-qa
Depends on:
Reported: 2015-11-04 17:26 UTC by martin
Modified: 2019-02-18 12:36 UTC (History)
3 users (show)

See Also:
pgj: maintainer-feedback+

A proposed fix for the problem (2.04 KB, patch)
2016-02-22 08:39 UTC, Gabor Pali
pgj: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description martin 2015-11-04 17:26:03 UTC

HSCOLOUR is a basic option for all Haskell ports. But it is also an option for hs-hscolour itself which leads to a dependency loop (depends directly on itself) when building or upgrading hs-hscolour.

HSCOLOUR should be excluded from this port configuration. It results in annoyances, when it is set accidently set (or globally in /etc/make.conf).

Comment 1 Gabor Pali freebsd_committer 2016-02-02 13:12:51 UTC
That might be easily the case.  We have fought with this one a lot back in the past, so I will need some time to think it over again.
Comment 2 Gabor Pali freebsd_committer 2016-02-22 08:39:14 UTC
Created attachment 167289 [details]
A proposed fix for the problem

I have created a patch for fixing this problem.  It also makes it possible to have colorized documentation for HsColour itself, so the option does not have to excluded for that port (as it was done before).

Please, try it and get back on the results.
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-01-09 14:56:43 UTC
Maintainer feedback?
Comment 4 Rene Ladan freebsd_committer 2018-11-06 21:35:38 UTC
Maintainer reset.
Comment 5 Mathieu Arnold freebsd_committer 2019-02-05 11:47:46 UTC
new maintainer
Comment 6 Gleb Popov freebsd_committer 2019-02-18 12:36:09 UTC
HSCOLOUR is gone now, so the problem should be solved.