Bug 204291

Summary: print/hs-hscolour: dependency loop with option HSCOLOUR
Product: Ports & Packages Reporter: martin
Component: Individual Port(s)Assignee: freebsd-haskell (Nobody) <haskell>
Status: Closed Overcome By Events    
Severity: Affects Many People CC: arrowd, pgj, w.schwarzenfeld
Priority: --- Keywords: needs-qa
Version: LatestFlags: pgj: maintainer-feedback+
Hardware: Any   
OS: Any   
Attachments:
Description Flags
A proposed fix for the problem pgj: maintainer-approval+

Description martin 2015-11-04 17:26:03 UTC 
Hi,

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).

--
Martin
Comment 1 Gabor Pali freebsd_committer freebsd_triage 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 freebsd_triage 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 2018-01-09 14:56:43 UTC 
Maintainer feedback?
Comment 4 Rene Ladan freebsd_committer freebsd_triage 2018-11-06 21:35:38 UTC 
Maintainer reset.
Comment 5 Mathieu Arnold freebsd_committer freebsd_triage 2019-02-05 11:47:46 UTC 
new maintainer
Comment 6 Gleb Popov freebsd_committer freebsd_triage 2019-02-18 12:36:09 UTC 
HSCOLOUR is gone now, so the problem should be solved.