| Summary: | media-fonts/iosevka: build from source to allow different styles to be installed | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Joonas Niilola <juippis> |
| Component: | Current packages | Assignee: | Arsen Arsenović <arsen> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | arsen, lynx1534, matthew, proteuss |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=769353 https://bugs.gentoo.org/show_bug.cgi?id=696466 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Joonas Niilola
2021-02-07 07:47:46 UTC
I'm looking into this. Is there a way to install npm packages for build without disabling network-sandbox? (In reply to Eternal Sorrow from comment #1) > I'm looking into this. Is there a way to install npm packages for build > without disabling network-sandbox? You can fetch the nodes, package tarball on your own, and put that to SRC_URI. Although didn't upstream kind of fix this bug already? are the current variants provided by the reworked ebuild sufficient to consider this bug resolved? declare -A MY_FONT_VARIANTS=( ["iosevka"]="Iosevka" ["iosevka-slab"]="Iosevka Slab" ["iosevka-curly"]="Iosevka Curly" ["iosevka-curly-slab"]="Iosevka Curly Slab" ["iosevka-ss01"]="Iosevka SS01" ["iosevka-ss02"]="Iosevka SS02" ["iosevka-ss03"]="Iosevka SS03" ["iosevka-ss04"]="Iosevka SS04" ["iosevka-ss05"]="Iosevka SS05" ["iosevka-ss06"]="Iosevka SS06" ["iosevka-ss07"]="Iosevka SS07" ["iosevka-ss08"]="Iosevka SS08" ["iosevka-ss09"]="Iosevka SS09" ["iosevka-ss10"]="Iosevka SS10" ["iosevka-ss11"]="Iosevka SS11" ["iosevka-ss12"]="Iosevka SS12" ["iosevka-ss13"]="Iosevka SS13" ["iosevka-ss14"]="Iosevka SS14" ["iosevka-ss15"]="Iosevka SS15" ["iosevka-ss16"]="Iosevka SS16" ["iosevka-ss17"]="Iosevka SS17" ["iosevka-ss18"]="Iosevka SS18" ["iosevka-aile"]="Iosevka Aile" ["iosevka-etoile"]="Iosevka Etoile" ) No, even remotely not. The number of possible combinations if you build the font manually is much higher than these predefined variants. (In reply to Sorrow from comment #4) > No, even remotely not. The number of possible combinations if you build the > font manually is much higher than these predefined variants. I don't think he meant mathematically. He was asking if the list currently installed, or perhaps a few more (list them) would be enough to make people happy. I also did not mean mathematically. I meant that none of the font variants in this list have all the options I would prefer. So having an ability to customize how the font looks would be better for me. Can't speak for "people" though. (In reply to Sorrow from comment #6) > I also did not mean mathematically. I meant that none of the font variants > in this list have all the options I would prefer. So having an ability to > customize how the font looks would be better for me. the number of possible products from the iosevka build system is indeed extremely high (i gave up on counting the magnitude of that number) the above list is an exhaustive list of the 'factory' provided superttc variants. savedconfig could definitely work. the external build dependencies don't worry me much, however, nodejs does. do we need some dist tarball with js deps vendored in to build fonts or such? i don't see any such asset attached to current releases. i presume you have experience building iosevka - does it only need the node deps and ttfautohint? thanks in advance (In reply to Sorrow from comment #6) > I also did not mean mathematically. I meant that none of the font variants > in this list have all the options I would prefer. So having an ability to > customize how the font looks would be better for me. ... so, to be clear, could you list the variansts you'd like? That's what we're interested in? (In reply to Sam James from comment #9) > (In reply to Sorrow from comment #6) > > I also did not mean mathematically. I meant that none of the font variants > > in this list have all the options I would prefer. So having an ability to > > customize how the font looks would be better for me. > > ... so, to be clear, could you list the variansts you'd like? That's what > we're interested in? that works today but you can also make custom remixes of the font, see https://typeof.net/Iosevka/specimen (In reply to Arsen Arsenović from comment #3) > are the current variants provided by the reworked ebuild sufficient to > consider this bug resolved? This ebuild now installs 24 ttc font collections each containing 162 fonts except Aile and Etoile that contain only 27 variants. A total of 3618 font variants. I think this bug is resolved. Thank you. >i presume you have experience building iosevka - does it only need the node deps and ttfautohint? ttfautohint, otfcc and node. But I built it very long time ago and don't remember the details. You'll need to download the list of npm packages and vendor them manually for node build system. >... so, to be clear, could you list the variansts you'd like? That's what we're interested in? I built Iosevka manually a long time ago and I already lost the config that I used then. So, to do that, I need to spend quite a lot time reading the config and fiddling the Iosevka specimen to find the variant that I like. I would prefer to do that when I will have the ability to build the font. |
