SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As for extracting them... it's three commands. "7z x" on the dmg file, "7z x" on the pkg file inside, "cpio -i" on the "Payload~" file inside the pkg file.
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
As for extracting them... it's three commands. "7z x" on the dmg file, "7z x" on the pkg file inside, "cpio -i" on the "Payload~" file inside the pkg file.
I'm interested in giving these fonts a look, but when I run "cpio -i" on the Payload~ file, it seems to just stall on not extract the file. Am I missing something?
I'm interested in giving these fonts a look, but when I run "cpio -i" on the Payload~ file, it seems to just stall on not extract the file. Am I missing something?
cpio doesn't use filenames, you have to REdirect the file into the cpio commandline, like
Code:
cpio -i"other options" < Payload_archive
See "man cpio" too for all the options (especially --make-directories or --preserve-modification-time.
cpio does need some getting used too, I admit, it really was meant to be used in a pipe.
For instance: from my "backup restore" script (which is using cpio archives)
(in which the "dd" can run on a different computer then the cpio, that's why the $RCMD in front of it). The $OPT can include options like--unconditional to overwrite already existing files.
I decided to go with Hack for my terminal font. For the entirely technical reason that it includes Powerline glyphs, and doesn't need to be "patched" to add them.
At this moment these SlackBuilds are from and for slackware64-14.2, but they also work with slackware-14.2.
I tried to make the minimal modificactions to the originals Slackbuilds.
There is not need to select a type of font rendering (Windows, Apple or Ubuntu)
since the "aim of infinality-bundle is to make use of the vast potential hidden in native Linux font rendering back-end".
Based on archfan infinality patches. https://github.com/archfan/infinality_bundle
Master branch contains sources and precompilled packages for slackware64-current.
If you use slackware-14.2 checkout slackware-14.2 branch.
diff --git .......
...
...
diff --git a/devel/ftoption.h b/devel/ftoption.h
--- a/devel/ftoption.h 2016-03-28 12:09:54.392246487 +0200
+++ b/devel/ftoption.h 2016-03-28 12:17:20.364039723 +0200
@@ -604,6 +604,16 @@ FT_BEGIN_HEADER
/* */
#define TT_CONFIG_OPTION_SUBPIXEL_HINTING
+ /*************************************************************************/
+ /* */
+ /* Define FT_CONFIG_OPTION_INFINALITY_PATCHSET if you want to enable */
+ /* all additional infinality patches, which are configured via env */
+ /* variables. */
+ /* */
+ /* This option requires TT_CONFIG_OPTION_SUBPIXEL_HINTING to */
+ /* defined. */
+ /* */
+#define FT_CONFIG_OPTION_INFINALITY_PATCHSET
/*************************************************************************/
/* */
But
the resulting files /tmp/bob-infinality-bundle/freetype-2.6.5/include/config/ftoption.h (after compilation)
(and 'ftoption.h' of freetype-2.6.5-x86_64-1.txz (after compilation))
do not have
+#define TT_CONFIG_OPTION_SUBPIXEL_HINTING
+#define FT_CONFIG_OPTION_INFINALITY_PATCHSET
These lines can be found only in /usr/include/config/ftoption.h.rej
AFAIU there is a conflict here.
So, if I want to get TT_CONFIG_OPTION_SUBPIXEL_HINTING,
I have to further set the file 'ftoption.h' manually in sources.
A buildable 2.10.4 patch is present in the freetype-2.10.4 branch of this repository. However, it fails to render glyphs at runtime resulting in segfaults for QT apps and broken rendering in GTK apps.
Looking for someone with FreeType experience who can help debug this issue and maybe even track down the root cause in the patched source.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.