| Summary: | [PATCH libXfont] rescan catalogue:<dir> fontpaths on directory changes | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Ademar Reis <ademar> | ||||||
| Component: | Lib/Xfont | Assignee: | Kristian Høgsberg <krh> | ||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | Keywords: | patch | ||||||
| Version: | git | ||||||||
| Hardware: | Other | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Ademar Reis
2007-07-12 10:54:46 UTC
Created attachment 10702 [details] [review] rescan catalogue:<dir> fontpaths on directory changes (b0rken) Comment on attachment 10702 [details] [review] rescan catalogue:<dir> fontpaths on directory changes (b0rken) this patch is broken, there's a duplicated closedir() call at the end. I'll attach a new one. Created attachment 10717 [details] [review] rescan catalogue:<dir> fontpaths on directory changes I'd like to keep the fontpath.d code simple and I don't think we should worry to much about the corner cases, since you can always just fall back and issue a xset fp rehash Also, for packaging, you can always just force the symlink, even though it's already there, which will bump the mtime on the fontpath.d dir. Sounds ok? The only problem is that it's not intuitive to touch fontpath.d/ to force a rehash (restarting xfs was) and users got used to the non need of running xset fp rehash. When packaging, we're subject to a race (a package may, for example, add the symlink as the package payload (%files) and run mkfontdir in %post). Or users may add the symlink manually and run mkfontdir later, etc. But the current code is not elegant (I don't like the double loop) and I guess a more beautiful solution would add considerable complexity. Ultimately it's your call... That's why I submmited the patch as a RFC. :-) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.