On 04.01.2018 07:25, Fabrice Desre wrote:
Does that mean that web pages see the api as exposed, but it doesn't > work? I guess the mock can "fail gracefully" and expect web sites to
process errors properly but in practice...
I'd like to get rid of the API at all. Don't wanna have any unused co
On 12/27/2017 06:57 AM, Emilio Cobos Álvarez wrote:
For what it's worth, I found the Bluetooth dependencies quite hard to deal
with when I tried to get Servo to compile on (somewhat older) CentOS VMs.
Maybe building without Bluetooth doesn't necessarily have to be a supported
configuration, but
On 01/04/2018 07:25 AM, Fabrice Desre wrote:
> On 12/27/2017 06:57 AM, Emilio Cobos Álvarez wrote:
>
>>> For what it's worth, I found the Bluetooth dependencies quite hard to
>>> deal
>>> with when I tried to get Servo to compile on (somewhat older) CentOS
>>> VMs.
>>> Maybe building without Bluet
On 12/27/2017 03:28 PM, Dirkjan Ochtman wrote:
> On Wed, Dec 27, 2017 at 2:23 PM, Emilio Cobos Álvarez
> wrote:
>
>> What's the point of disabling it at compile time instead of at runtime?
>>
>> Supporting different build configurations is more painful than a runtime
>> check, requires more wor
On Wed, Dec 27, 2017 at 2:23 PM, Emilio Cobos Álvarez
wrote:
> What's the point of disabling it at compile time instead of at runtime?
>
> Supporting different build configurations is more painful than a runtime
> check, requires more work, and breaks more easily / often.
>
For what it's worth,
On 12/27/2017 02:00 AM, Enrico Weigelt, metux IT consult via dev-servo
wrote:
> Hi folks,
>
> I've made some hacks for making bluetooth optional.
> (no bit of bt compiled at all)
>
> https://github.com/metux/servo/commits/HACK_cfg_bluetooth
>
>
> The biggest problem yet is missing opt-out of we
6 matches
Mail list logo
