Date: Sun, 28 Aug 2011 19:41:02 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: OPTIONS framework bug vs. SSL issues (was: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken) Message-ID: <4E5A7DAE.8090904@FreeBSD.org> In-Reply-To: <CADLo838TqZjGH__KNTu3A0wVEnX%2B225HFhBmiEjqj=456y6iag@mail.gmail.com> References: <4E5A48AC.6050201@eskk.nu> <CADLo838TqZjGH__KNTu3A0wVEnX%2B225HFhBmiEjqj=456y6iag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.08.2011 16:33, schrieb Chris Rees: > make -C /usr/ports/print/cups-client config, disable TLS. > > Chris > On 28 Aug 2011 15:15, "Leslie Jensen" <leslie@eskk.nu> wrote: >> >> Following the instructions in /usr/ports/UPDATING I issued the command >> >> >> portmaster -r libnotify-0 >> >> And after a while I get this error >> >> Dependency check complete for print/cups-client >> libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> apache-ant-1.8.2 >> >> jdk-1.6.0.3p4_25 >> cups-client-1.4.6 >> ===> Cleaning for cups-client-1.4.8 >> >> ===> cups-client-1.4.8 is marked as broken: gnutls does not support >> threads yet. >> *** Error code 1 >> >> Stop in /usr/ports/print/cups-client Greetings, just a brain flash: bsd.port.mk currently re-prompts OPTIONS if they've changed, for instance, through addition. Should we change this feature in b.p.mk so that it also re-prompt the user when the defaults have changed? Or should the CUPS port remove the GNUTLS offering altogether until either GNUTLS is multithreaded, CUPS single-threaded, or CUPS offers another library? Would it help the licensing mess to use NSS instead? I recall Fedora working on API-compatible layers so they could unify OpenSSL/GNUTLS/NSS APIs and rebase everything onto NSS. I haven't checked lately though what the status is. Best, Matthias
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E5A7DAE.8090904>