fontconfig (or the fonts ports/packages) are supposed to run fc-cache.
I also noticed it has problems with some fonts, so we may end up with a
not complete cache in this version.
This should fix the build on pointyhat (cache files left after pkg_delete).
While I'm here use a link to the native fonts.conf, we don't need our
own here.
- use fixed plists [1]
- category "linux" added to those ports without it [1]
- update some ports to a recent FC3 one [1]
- remove plists/... for Alpha (there's no support since linux_base-8 for
Alpha anymore)
- don't hardcode version numbers in some plists, use PLIST_SUB instead
(any errors are mine, don't keep them, send them to me)
Regarding linux-ungif I declare a maintainer timeout (one month, Boris tried
to contact the maintainer) and also pull the "sweeping commit"-card (the
port which it uses as some kind of master port can not be used for this
anymore). Besides this, I don't think he will be upset when other people
do the work instead of adding an entry to his TODO list. :-)
This commit brings us just before the switch of the default linux base
port to the fc3 one, modulo some bugs which may appear. So:
Beta testers wanted!
To test:
sed -i.old -e 's:linux-XFree86-libs:linux-xorg-libs:' /usr/ports/Mk/bsd.port.mk
echo OVERRIDE_LINUX_BASE_PORT=fc3 >> /etc/make.conf
portupgrade -f -o emulators/linux_base-fc3 -f linux_base-8
portupgrade -o x11/linux-xorg-libs linux-XFree86-libs
portupgrade linux-\*
The first two steps are necessary to switch to fc3 as the new default linux
base port, the last 3 steps to upgrade to fc3.
And feel free to send a big "Thank you!" to Boris, he did a lot of the work!
I just provided some hints and answered some questions (besides from
committing all the necessary changes for FC3 and doing some minor
changes+comments/improvements to/of his work), even when he tries to tell
you something else. ;-)
Submitted by: Boris Samorodov <bsam@ipt.ru> [1]
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
PR.
Thanks for contributing.
Since the acroread7 port is a somewhat important port for our users, I
will hand it over to emulation@ if no _active_ *committer* takes it
before the ports freeze.
While I'm here:
- fix a little nit in the csound port (I think the intention was to
create no backup file instead of creating one with a "-e" extension)
- set ARCH to i386 in the amd64 case for the acroread7 port. This
is a work-around to be able to install everything when a dependency
is not already installed (ARCH is read-only in sub-makes, so the
dependencies can't change it). This should be removed when the
dependencies are fixed or converted to use bsd.linux-rpm.mk. [1]
Not objected to by: portmgr (explicit: krion; silence: rest)
Maintainer timeout: ~4 months
Submitted by: Sangwoo Shim <sangwoos@gmail.com> [1]
PR: 87985 [1]
published, including Elham, Terafik, Terafik Bold, Titr, Roya, Roya Bold,
Koodak, Nazli, Nazli Bold, and Homa. The main advantage over legacy fonts is
compliance with the Unicode, ISIRI 6219, and OpenType standards, and the
addition of required but missing glyphs for Persian information processing. The
fonts are highly recommended if you care for proper Persian display on your
computers.
PR: ports/92905
Submitted by: Babak Farrokhi <babak@farrokhi.net>
this port installs encodings, try to remove them upon uninstallation, so
removing of directories has a chance to succeed. Just in case some user
has for some reason put fonts under these directories, be nice and try to
regenerate cache file and remove it again only if it is empty.
On installation try running fc-cache for directory where fonts from this
port are installed and don't complain if fc-cache (from fontconfig) is
missing. Do a bit more dancing on uninstall, just in case users have their
own fonts installed in same directory:
- first remove fonts.cache-1 if it is there since it won't be accurate
after fonts from this port are gone anyway,
- next try to regenerate cache with fc-cache for this directory
- if previous step generates empty cache file, remove it
If directory contained only fonts from this port, it should get properly
removed at the end. If there were other fonts there and fontconfig is
installed, this will leave proper cache file for remaining fonts behind
after uninstall of this port.
this port installs encodings, try to remove them upon uninstallation, so
removing of directories has a chance to succeed. Just in case some user
has for some reason put fonts under these directories, be nice and try to
regenerate cache file and remove it again only if it is empty.
Prodded by: kris' new pointyhat checks
On installation try running fc-cache for directory where fonts from this
port are installed and don't complain if fc-cache (from fontconfig) is
missing. Do a bit more dancing on uninstall, just in case users have their
own fonts installed in same directory:
- first remove fonts.cache-1 if it is there since it won't be accurate
after fonts from this port are gone anyway,
- next try to regenerate cache with fc-cache for this directory
- if previous step generates empty cache file, remove it
If directory contained only fonts from this port, it should get properly
removed at the end. If there were other fonts there and fontconfig is
installed, this will leave proper cache file for remaining fonts behind
after uninstall of this port.
