'font-alias' breaks other xorg font packages when installed in a single profile

OpenSubmitted by Alex Kost.
Details
3 participants
  • Alex Kost
  • Eric Bavier
  • Ludovic Courtès
Owner
unassigned
Severity
normal
A
A
Alex Kost wrote on 6 Dec 2015 10:19
(address . bug-guix@gnu.org)(name . Eric Bavier)(address . bavier@member.fsf.org)
874mfwexy6.fsf@gmail.com
I install several xorg font packages (font-adobe75dpi, font-adobe100dpi,
font-misc-misc and font-alias) in one of my profiles, and point my Xorg
font path to this directory. Previously it worked fine, but after
commit bf9655f¹, I cannot use this anymore, because the empty
"fonts.dir" files from 'font-alias' packages override the proper
"fonts.dir" files from the other packages.

So since it was a workaround for Xorg server behaviour, I wonder would
it be possible to modify 'xorg-server' package instead? So that along
with directories with "fonts.dir" files, Xorg server would also handle
directories that have "fonts.alias" files.

Anyway, I don't insist on reverting this commit, as I'm rather happy
using the following package (Guix is great!):

(define-public font-alias-pure
(package
(inherit font-alias)
(name "font-alias-pure")
(arguments '())
(synopsis (string-append (package-synopsis font-alias)
" (upstream package without modifications)"))))


--
Alex
L
L
Ludovic Courtès wrote on 9 Dec 2015 15:05
(name . Alex Kost)(address . alezost@gmail.com)
871tavsonr.fsf@gnu.org
Alex Kost <alezost@gmail.com> skribis:

Toggle quote (7 lines)
> I install several xorg font packages (font-adobe75dpi, font-adobe100dpi,
> font-misc-misc and font-alias) in one of my profiles, and point my Xorg
> font path to this directory. Previously it worked fine, but after
> commit bf9655f¹, I cannot use this anymore, because the empty
> "fonts.dir" files from 'font-alias' packages override the proper
> "fonts.dir" files from the other packages.

D’oh!

Toggle quote (5 lines)
> So since it was a workaround for Xorg server behaviour, I wonder would
> it be possible to modify 'xorg-server' package instead? So that along
> with directories with "fonts.dir" files, Xorg server would also handle
> directories that have "fonts.alias" files.

It seems we need something along these lines, indeed.

WDYT Eric?

Thanks,
Ludo’.
L
L
Ludovic Courtès wrote on 12 Dec 2015 18:37
(name . Eric Bavier)(address . bavier@member.fsf.org)
87d1ub36vw.fsf@gnu.org
Eric Bavier <bavier@member.fsf.org> skribis:

Toggle quote (3 lines)
> Since xorg-server lacks AFAIK any environment variables to set the font
> path we cannot consider moving fonts to namespaced directories.

Hmm.

Toggle quote (4 lines)
> Instead, we might want to consider ignoring fonts.dir files from the
> union build if possible and then running mkfontsdir at profile creation
> time.

We could always do that but, shouldn’t we fix the X font server instead?
(Easier said than done, I admit, unless there are patches floating around.)

Thanks,
Ludo’.
E
E
Eric Bavier wrote on 12 Dec 2015 03:06
(name . Ludovic Courtès)(address . ludo@gnu.org)
20151211200627.04c9c1b1@member.fsf.org
On Wed, 09 Dec 2015 15:05:28 +0100
ludo@gnu.org (Ludovic Courtès) wrote:

Toggle quote (11 lines)
> Alex Kost <alezost@gmail.com> skribis:
>
> > I install several xorg font packages (font-adobe75dpi, font-adobe100dpi,
> > font-misc-misc and font-alias) in one of my profiles, and point my Xorg
> > font path to this directory. Previously it worked fine, but after
> > commit bf9655f¹, I cannot use this anymore, because the empty
> > "fonts.dir" files from 'font-alias' packages override the proper
> > "fonts.dir" files from the other packages.
>
> D’oh!

Oops indeed.

Toggle quote (7 lines)
> > So since it was a workaround for Xorg server behaviour, I wonder would
> > it be possible to modify 'xorg-server' package instead? So that along
> > with directories with "fonts.dir" files, Xorg server would also handle
> > directories that have "fonts.alias" files.
>
> It seems we need something along these lines, indeed.

That may help in the specific case of the font-alias package. It would
not help in the long run however. We currently have a rather
limited number of X11 fonts in Guix, just the adobe fonts to be
precise. We'll run into the same 'fonts.dir' collision issues once
other X11 fonts are packaged and installed in a profile alongside other
fonts.

E.g. installing font-adobe75dpi and a future font-bitstream75dpi would
produce a collision on the fonts.dir files from each package, and
ultimately only one of the fonts would be available to the user.

Since xorg-server lacks AFAIK any environment variables to set the font
path we cannot consider moving fonts to namespaced directories.
Instead, we might want to consider ignoring fonts.dir files from the
union build if possible and then running mkfontsdir at profile creation
time.

`~Eric
?