Ability to specify terminfo destination independently from `data-dir` #569

Closed
opened 5 months ago by sterni · 1 comments
sterni commented 5 months ago

In nix we have a concept of multiple package outputs which can be used to reduce the amount of downloaded data when you need a specific subset of a package (e. g. if you link against a library, you don't need to install the output with include at run time etc.).

We could use this to provide foot's terminfo for servers by having a terminfo output which can be installed without the default output containing foot's binaries etc.

Currently the location the terminfo is installed to depends on data-dir which is also where the license etc. goes. Would it be possible to add a meson flag to specify the target directory for the terminfo files?

If it is too much hassle, don't bother since we can probably achieve the same result with a call to mv.

In nix we have a concept of multiple package outputs which can be used to reduce the amount of downloaded data when you need a specific subset of a package (e. g. if you link against a library, you don't need to install the output with `include` at run time etc.). We could use this to provide foot's terminfo for servers by having a `terminfo` output which can be installed without the default output containing foot's binaries etc. Currently the location the terminfo is installed to depends on `data-dir` which is also where the license etc. goes. Would it be possible to add a meson flag to specify the target directory for the terminfo files? If it is too much hassle, don't bother since we can probably achieve the same result with a call to `mv`.
Owner

I wouldn't mind it. But, I'm starting to think it's better to not build the terminfo at all as part of the regular build process.

Since the terminfo almost always is packaged separately (and rightly so), it's mostly just annoying to have it be part of the normal build process. All you really need to do is run tic -x -e foot,foot-direct foot.info.

This is what the Arch AUR package does.

How would that work out for nix?

I wouldn't mind it. But, I'm starting to think it's better to not build the terminfo at all as part of the regular build process. Since the terminfo almost always is packaged separately (and rightly so), it's mostly just annoying to have it be part of the normal build process. All you _really_ need to do is run `tic -x -e foot,foot-direct foot.info`. This is what the [Arch AUR package](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=foot-terminfo) does. How would that work out for nix?
dnkl closed this issue 4 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.