Crates.io | viro |
lib.rs | viro |
version | 1.0.4 |
source | src |
created_at | 2021-08-23 04:23:00.677564 |
updated_at | 2024-01-25 17:31:23.738118 |
description | Loads your environment so you don't have to. |
homepage | |
repository | https://codeberg.org/clarfonthey/viro |
max_upload_size | |
id | 440945 |
size | 61,681 |
Loads your environment so you don't have to.
Offers a data structure for serializing and deserializing environment variables, to allow for easy
loading of /etc/profile
scripts in non-POSIX shells like fish
. The viro
binary is only
available for unix-based systems at the moment; see the "Roadmap" section of this README for
details.
Available via the Anti-Capitalist Software License for individuals, non-profit organisations, and worker-owned businesses.
First, build viro
for your system with the sync-stdio
feature and install it in /usr/bin
,
alongside the viro-profile
script.
Depending on whether you want to use systemd or no d, merge the /usr
provided in either
systemd/usr
or nod/usr
with your own.
Because bash does not have a standardized config directory, you will need to source the scripts in
/usr/share/bash/bashrc.d
in order to make this work. If you chose to use systemd, you must also
enable the profile.service
for your user.
For now, the viro
crate has no actual support for converting environment variables into byte
sequences, and the viro
binary simply assumes that the conversion is trivial, as it is on
POSIX-compliant systems. However, on systems like Windows, a more complicated conversion will be
necessary to convert between genuine environment variables and byte slices using a format like
WTF-8.
Additionally, there are currently no attempts to escape \x3D
(equals sign) and \x00
(NUL) bytes
when outputting variables, and this simply alters the output. A future version of this crate will
want to offer these, but I have no plans to implement this at the moment.