lib-satysfi is copied to unexpected directory when `opam install satysfi` about satysfi HOT 23 CLOSED

Thanks. We can wait @gfngfn to fix font issue #13 #17 (since I don't know much about font) and I can fix build issue later (#21, #40)

from satysfi.

I am unsure but embedding $PREFIX into the source code in compile-time or using relative path would work, I guess.

from satysfi.

@objmagic, please consider free alternatives I listed too if you work on the font issue.
IMHO, using Latin Modern and/or TeX Gyre for Latin scripts and IPAex for Japanese scripts is a lightweight solution.

(Note that Latin Modern and some of TeX Gyre fonts already have corresponding OpenType Math fonts, so they will get harmonized results without much investigation after we get configurable math font feature.)

from satysfi.

@objmagic additional note for the font issue https://twitter.com/bd_gfngfn/status/964779203869556737

from satysfi.

Not yet. We still need to execute cp -R "$(opam config var prefix)/share/satysfi" "${HOME}/.satysfi" as a workaround after installation. #109 addresses this, but it has not been reviewed yet.

from satysfi.

How about just making SATySFi $PREFIX-friendly? (At least setup_root_dirs will need some changes.) Maybe I am missing the point, though...
PATH-like environment variable would be helpful anyway.

from satysfi.

Survey: TeX uses multiple TEXMF.

References (in Japanese):

• TeX のディレクトリ構成 -- TeX Wiki
• texmf.cnf ファイル -- TeX Wiki

from satysfi.

@omasanori What do you think about the method to remember $PREFIX?

from satysfi.

we shouldn't copy libraries under /usr/local/share

agree. We cannot assume every user has access to /usr/local

from satysfi.

Yes, root_dirs is now hard-coded and is not configurable.
I was aware, when I wrote that patch, that that may cause some problems, but could not find a neat way to tell opam to modify the source code and embed installation directory strings (e.g. /usr/local or ~/.opam/4.06.0/). (Is there?)

One possible workaround is to get opam installation directory at run time and append it to satysfi_root_dirs with less priority than ~/.satysfi. Thoughts?

from satysfi.

@nyuichi Thanks for your comment! I almost agree with you. I also thought of getting the OPAM prefix at run time by running opam config var prefix, however I noticed that the same problem will occur if other $PREFIX is set at compile time. So I'm seeking more general solution.

from satysfi.

I can make a large clean up in #21 to address many issues including this one later when I have time. But before this I'd like to have font dependency issue resolved

from satysfi.

@nekketsuuu

Right. That's not a fix but just a workaround, though I think it should work fine for most users. Meanwhile, I await @objmagic's fix, leaving this issue as it is.

from satysfi.

@objmagic

Are you still working on this? If you don't have time, I can write a patch instead.

from satysfi.

Has the problem solved?

from satysfi.

@gfngfn How's #109 going? I think it's great to resolve this issue for easy installation of SATySFi.

from satysfi.

FYI, for workaround, I made a tool https://github.com/na4zagin3/satyrographos which copies the directories under $(opam config var prefix)/share/satysfi/* to $HOME/.satysfi/dist with merging.

from satysfi.

@nekketsuuu do you mind to close this PR as the lib-satysfi is not installed under the OPAM registory now?

from satysfi.

@na4zagin3 Which commits or pull requests do you think of as that change?

from satysfi.

@nekketsuuu 3c1bd3c must be it.

from satysfi.

If #149 is merged, the dist library will be installed into OPAM registry again, fyi.

from satysfi.

Ah, I remember that. Personally I feel that does not resolve the core of this problem best, but this issue is fixed as you said.

I'm closing this issue, but feel free to reopen this or report an related issue if needed.

from satysfi.

Ah, I missed this PR actually includes a proposal to use environment variables.. I'd update the title and the description..

from satysfi.