Re: Chrome and noto

2018-03-07 Thread Mark Dixon
Seems like they’re making that the default.  

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226255

Mark 

> On 6 Mar 2018, at 18:46, Tobias C. Berner  wrote:
> 
> Hi Mark
> 
> We recently added a way to toggle the dependency on noto vs noto-lite in 
> x11/plasma5-plasma-integration, 
> if you switch that one to "BIG" then, you will get at least no longer a 
> conflict with chromium.
> 
> If you really would like to save on the disk-space, you can also edit 
> www/chromium/Makefile to read
>noto-lite>0:x11-fonts/noto-lite 
> instead of
>   noto>0:x11-fonts/noto
> as it does now, and rebuilt it (which should work [tm]). 
> 
> 
> 
> mfg Tobias
> 
>> On 6 March 2018 at 09:13, Mark Dixon  wrote:
>> Hi all,
>> 
>> Chrome seems to have added a dependency on x11-fonts/noto which seems to be 
>> conflicting with KDE's x11-fonts/noto-lite. 
>> 
>> Is there anything we can do about this? Not sure if depending on the full 
>> 800Mb noto is a great move on their part.
>> 
>> Mark
> 


Re: Chrome and noto

2018-03-06 Thread Tobias C. Berner
Hi Mark

We recently added a way to toggle the dependency on noto vs noto-lite in
x11/plasma5-plasma-integration,
if you switch that one to "BIG" then, you will get at least no longer a
conflict with chromium.

If you really would like to save on the disk-space, you can also edit
www/chromium/Makefile to read
   noto-lite>0:x11-fonts/noto-lite
instead of
  noto>0:x11-fonts/noto
as it does now, and rebuilt it (which should work [tm]).



mfg Tobias

On 6 March 2018 at 09:13, Mark Dixon  wrote:

> Hi all,
>
> Chrome seems to have added a dependency on x11-fonts/noto which seems to
> be conflicting with KDE's x11-fonts/noto-lite.
>
> Is there anything we can do about this? Not sure if depending on the full
> 800Mb noto is a great move on their part.
>
> Mark
>