Setup the font path to built-ins only.

Setup the font path to built-ins only.

Change-Id: I5aa09b108c4deb230cd7286d979344b15685c376

BUG=chromium-os:13061
TEST=Ran X, verified that the xorg log doesn't have the font path any more.

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=321885c

[Daniel Kurtz, 2011-04-22 01:54:37]

Please bump ebuild rev.

[marcheu, 2011-04-22 02:11:53]

On 2011/04/22 01:54:37, Daniel Kurtz wrote:
> Please bump ebuild rev.

Done, PTAL.

[Daniel Kurtz, 2011-04-22 02:22:41]

1.10.1-r1

[marcheu, 2011-04-22 02:23:41]

On Thu, Apr 21, 2011 at 19:22, <djkurtz@chromium.org> wrote:

> 1.10.1-r1
>
> It's not in use, I'm not upreving it until then.

[Daniel Kurtz, 2011-04-22 02:29:00]

But you are making changes from the stock upstream version, so please uprev.

On Fri, Apr 22, 2011 at 10:23 AM, Stéphane Marchesin
<marcheu@chromium.org>wrote:

>
>
> On Thu, Apr 21, 2011 at 19:22, <djkurtz@chromium.org> wrote:
>
>> 1.10.1-r1
>>
>> It's not in use, I'm not upreving it until then.
>

[marcheu, 2011-04-22 02:29:35]

On 2011/04/22 02:29:00, Daniel Kurtz wrote:
> But you are making changes from the stock upstream version, so please uprev.
> 

This is not the upstream version at all.

[Daniel Kurtz, 2011-04-22 03:36:54]

That is even more unfortunate.
Is there a reason we can't fetch upstream 1.10.1 as the base version, and apply
our custom patches to it as 1.10.1-r1?

[marcheu, 2011-04-22 05:24:21]

On 2011/04/22 03:36:54, Daniel Kurtz wrote:
> That is even more unfortunate.
> Is there a reason we can't fetch upstream 1.10.1 as the base version, and
apply
> our custom patches to it as 1.10.1-r1?

No. We have a very different set of needs.

Anyway, if you don't want to LGTM, let me know I'll drop this patch.

[Daniel Kurtz, 2011-04-22 05:30:55]

>
> On Thu, Apr 21, 2011 at 19:22, <djkurtz@chromium.org> wrote:
>
>> 1.10.1-r1
>>
>> It's not in use, I'm not upreving it until then.
>

OK, then LGTM.