Reviewed-on: #9 Co-authored-by: ltdk <email@example.com> Co-committed-by: ltdk <firstname.lastname@example.org>
|4 months ago|
|nod/usr/share||5 months ago|
|src||4 months ago|
|systemd/usr||5 months ago|
|.editorconfig||5 months ago|
|.gitignore||5 months ago|
|CHANGELOG.md||4 months ago|
|Cargo.lock||4 months ago|
|Cargo.toml||4 months ago|
|LICENSE.md||5 months ago|
|Makefile||5 months ago|
|README.md||5 months ago|
|viro-profile||5 months ago|
Loads your environment so you don't have to.
Offers a data structure for serializing and deserializing environment variables, to allow for easy
/etc/profile scripts in non-POSIX shells like
viro binary is only
available for unix-based systems at the moment; see the "Roadmap" section of this README for
Available via the Anti-Capitalist Software License for individuals, non-profit organisations, and worker-owned businesses.
viro for your system with the
sync-stdio feature and install it in
Depending on whether you want to use systemd or no d, merge the
/usr provided in either
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
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
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.