12:13 a.m.
Hi,
I've added the file triggers for fonts in rawhide to update the cache
and dropped the call of fc-cache in %post/un from fontpackages. we may
need to rebuild all of font packages eventually though, please let me
know if you see any issues about it.
--
Akira TAGOH
4:43 a.m.
No need to modify. all the trick is done in the rpm macro that
fontpackages provides. so the font package maintainers just need to
rebuild it when they need to do something for other purpose. I assume
all of the transition should be done sooner or later when we will have
mass-rebuild for others.
On Mon, Sep 7, 2015 at 6:09 PM, Alexander Ploumistos
<alex.ploumistos(a)gmail.com> wrote:
Does this mean that we need to modify spec files for font packages?
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
Akira TAGOH
11:24 a.m.
On Mon, Sep 07, 2015 at 02:13:28PM +0900, Akira TAGOH wrote:
I've added the file triggers for fonts in rawhide to update the
cache
and dropped the call of fc-cache in %post/un from fontpackages. we may
need to rebuild all of font packages eventually though, please let me
know if you see any issues about it.
I just discovered that trying to install the Noto font family in
Software will reliably kill a (relatively powerful) system. This will
fix that, right?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
12:35 p.m.
----- Mail original -----
De: "Matthew Miller"
I just discovered that trying to install the Noto font family in
Software will reliably kill a (relatively powerful) system. This will
fix that, right?
I fear that's the cause, not the solution. The previous solution was very careful to
only call fontconfig once per changed font directory. Unless the triggers are filtered
they will launch once per font *file*. So a killer for packages with many font files (like
noto)
However, that's just a suspicion for now. I haven't really investigated so far,
and the system noto killed my side is not so powerful (chromebook)
At minima all packages with fonts should be mass rebuilt now, otherwise fontconfig cache
refresh will be called both with the new method via triggers in the fontconfig package,
and by the scriplets in current font packages. But I doubt this doubling alone is
sufficient to cause the effect we've both seen
To be fair the change was done due to missed cache updates, I'd have chosen
heavy-handedness myself in that case.
1:39 p.m.
On Thu, Sep 10, 2015 at 07:35:03PM +0200, nicolas.mailhot(a)laposte.net wrote:
> I just discovered that trying to install the Noto font family
in
> Software will reliably kill a (relatively powerful) system. This will
> fix that, right?
I fear that's the cause, not the solution. The previous solution was
very careful to only call fontconfig once per changed font directory.
Unless the triggers are filtered they will launch once per font
*file*. So a killer for packages with many font files (like noto)
The initial message here (see subject line, actually) says that the
change was made in Rawhide. My system was F23, so it's gotta be the old
thing not the new one, right?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
10:09 p.m.
On Fri, Sep 11, 2015 at 3:39 AM, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
On Thu, Sep 10, 2015 at 07:35:03PM +0200, nicolas.mailhot(a)laposte.net
wrote:
> > I just discovered that trying to install the Noto font family in
> > Software will reliably kill a (relatively powerful) system. This will
> > fix that, right?
> I fear that's the cause, not the solution. The previous solution was
> very careful to only call fontconfig once per changed font directory.
> Unless the triggers are filtered they will launch once per font
> *file*. So a killer for packages with many font files (like noto)
The initial message here (see subject line, actually) says that the
change was made in Rawhide. My system was F23, so it's gotta be the old
thing not the new one, right?
All of font packages needs to be rebuilt to complete the transition
for this and doing it now may be a bit late? otherwise I'm willing to
work on that though.
--
Akira TAGOH
9:38 a.m.
On Fri, Sep 11, 2015 at 12:09:22PM +0900, Akira TAGOH wrote:
> On Thu, Sep 10, 2015 at 07:35:03PM +0200,
nicolas.mailhot(a)laposte.net wrote:
>> > I just discovered that trying to install the Noto font family in
>> > Software will reliably kill a (relatively powerful) system. This will
>> > fix that, right?
>> I fear that's the cause, not the solution. The previous solution was
>> very careful to only call fontconfig once per changed font directory.
>> Unless the triggers are filtered they will launch once per font
>> *file*. So a killer for packages with many font files (like noto)
> The initial message here (see subject line, actually) says that the
> change was made in Rawhide. My system was F23, so it's gotta be the old
> thing not the new one, right?
All of font packages needs to be rebuilt to complete the transition
for this and doing it now may be a bit late? otherwise I'm willing to
work on that though.
Well, I'm still unclear on all of the above. Will doing this in F23:
a) fix the installing-Noto-kills-your-system issue
b) make that issue worse
c) no change?
d) something else!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
11:03 p.m.
2015/09/11 23:38 "Matthew Miller" <mattdm(a)fedoraproject.org>:
Well, I'm still unclear on all of the above. Will doing this in F23:
a) fix the installing-Noto-kills-your-system issue
b) make that issue worse
c) no change?
d) something else!
I'm expecting a). after this change, fc-cache will be called once per
transaction so you won't see it so many times anymore as long as you
install them together.
Is it what you are concerned right?
3141
days inactive
3146
days old
9 comments
4 participants
participants (4)
-
Akira TAGOH -
Alexander Ploumistos -
Matthew Miller -
Nicolas Mailhot