Re: [ptxdist] [PATCH] xorg-fonts: make all xorg-font packages tristate

2018-07-31 Thread Baeuerle, Florian
Hi, Am Dienstag, den 31.07.2018, 11:31 +0200 schrieb Michael Olbrich: > Hi, > > On Tue, Jul 31, 2018 at 08:54:14AM +, Baeuerle, Florian wrote: > > the approach works for me, at least for completely selecting or deselecting > > a font via collection. You have to select MENU_FONTS and

Re: [ptxdist] [PATCH] xorg-fonts: make all xorg-font packages tristate

2018-07-31 Thread Michael Olbrich
Hi, On Tue, Jul 31, 2018 at 08:54:14AM +, Baeuerle, Florian wrote: > the approach works for me, at least for completely selecting or deselecting > a font via collection. You have to select MENU_FONTS and XORG_FONT_TTF as > module. I have a package which then selects noto fonts as dependency.

Re: [ptxdist] [PATCH] xorg-fonts: make all xorg-font packages tristate

2018-07-31 Thread Baeuerle, Florian
Hi Michael, the approach works for me, at least for completely selecting or deselecting a font via collection. You have to select MENU_FONTS and XORG_FONT_TTF as module. I have a package which then selects noto fonts as dependency. When deselecting this package in a collection, I end up with a

Re: [ptxdist] [PATCH] xorg-fonts: make all xorg-font packages tristate

2018-07-30 Thread Michael Olbrich
No, tristate is for collections. And all font files are currently dumped into one xorg-fonts ipkg. This is realy ugly and does not work with collections. It may be possible to create individual ipkgs for each package. But that's not so simple because we generate index files at the end. I don't

[ptxdist] [PATCH] xorg-fonts: make all xorg-font packages tristate

2018-07-30 Thread Florian Bäuerle
--- rules/graphics_and_multimedia.in | 6 +++--- rules/xorg-font-100dpi-trans.in | 8 rules/xorg-font-100dpi.in| 2 +- rules/xorg-font-75dpi-trans.in | 8 rules/xorg-font-75dpi.in | 2 +-