Loads your environment so you don't have to.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
ltdk ace7073672 Refactor viro-profile 7 months ago
nod/usr/share Initial commit 1 year ago
src Fixed typo 10 months ago
systemd/usr Initial commit 1 year ago
usr/bin Refactor viro-profile 7 months ago
.editorconfig Initial commit 1 year ago
.gitignore Initial commit 1 year ago
CHANGELOG.md Refactor viro-profile 7 months ago
Cargo.lock Breaking: use tokio instead of async_std and futures crates 10 months ago
Cargo.toml Breaking: use tokio instead of async_std and futures crates 10 months ago
LICENSE.md Initial commit 1 year ago
Makefile Initial commit 1 year ago
README.md Refactor viro-profile 7 months ago

README.md

viro

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.

License

Available via the Anti-Capitalist Software License for individuals, non-profit organisations, and worker-owned businesses.

Installation

First, build viro for your system with the sync-stdio feature and copy it into usr/bin in this directory.

Depending on whether you want to use systemd or no d, merge the /usr provided in either systemd/usr or nod/usr with the common usr directory provided here.

Finally, merge the complete usr directory with your own /usr or /usr/local.

Usage

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.

Roadmap

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.