Date: Sun, 03 Jan 2021 17:32:14 +0000 From: bugzilla-noreply@freebsd.org To: xfce@FreeBSD.org Subject: [Bug 252355] sysutils/garcon: fail to build Message-ID: <bug-252355-28711-BZgJV3wDky@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252355-28711@https.bugs.freebsd.org/bugzilla/> References: <bug-252355-28711@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252355 --- Comment #11 from Guido Falsi <madpilot@FreeBSD.org> --- Checking dependency options is not supported by the ports tree and I think = it is dangerous and unwarranted to add hacks to work it in certain ports. Anyway, in this case, garcon does have a configure flag to enable and disab= le gir support. So I'm adding a GIR option to it too. There is no way to really prevent users from setting contrasting options wh= ich will cause something to break. The fact an option could cause some other po= rt to break if disabled is not enough to warrant removing it. Maybe some user = is not interested in that extra port and does not care if it breaks. If the upstream provides the option to disable gir support, why should we prevent = it? Anyway I also noticed that garcon builds git files itself if gir support is explicitly enabled and doesn't when it's not disabled. For some reason it g= ets confused with autodetection when it's dependencies don't include git suppor= t. So adding a GIR option to garcon makes it "more complete". I'm almost done with such a patch, I'll commit it later after some more testing. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252355-28711-BZgJV3wDky>