ybox 0.9.8.1__tar.gz → 0.9.9__tar.gz

{ybox-0.9.8.1/src/ybox.egg-info → ybox-0.9.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: ybox
-Version: 0.9.8.1
+Version: 0.9.9
 Summary: Securely run Linux distribution inside a container
 Author-email: Sumedh Wale <sumwale@yahoo.com>, Vishal Rao <vishalrao@gmail.com>
 License: Copyright (c) 2024-2025 Sumedh Wale and contributors
@@ -342,10 +342,10 @@ ybox-destroy ybox-arch_apps
 ```
 
 Will destroy the `apps` container created in the example before. This does not delete the
-$HOME files, nor does it delete the shared root directory (if enabled). Hence, if you create
+`$HOME` files, nor does it delete the shared root directory (if enabled). Hence, if you create
 a new container having the same shared root, then it will inherit everything installed
 previously. Likewise, if you create the container with the same profile again, then it
-will also have the $HOME as before if you do not explicitly delete the directories
+will also have the `$HOME` as before if you do not explicitly delete the directories
 in `~/.local/share/ybox`.
 
 
@@ -374,10 +374,10 @@ ybox-cmd ybox-arch_apps -- ls -l
 ```
 
 The default profiles also link the .bashrc and starship configuration files from your host
-$HOME directory by default, so you should see the same bash shell configuration as in your
+`$HOME` directory by default, so you should see the same bash shell configuration as in your
 host. These are linked in read-only mode, so if you want to change these auto-linked
 configuration files inside the container, then you will need to create a copy from the symlink
-first (but then it will lose the link from the host $HOME).
+first (but then it will lose the link from the host `$HOME`).
 
 A shell on a container will act like a native Linux distribution environment for most purposes.
 The one prominent missing thing is systemd which is not enabled deliberately since it requires

{ybox-0.9.8.1 → ybox-0.9.9}/README.md

@@ -298,10 +298,10 @@ ybox-destroy ybox-arch_apps
 ```
 
 Will destroy the `apps` container created in the example before. This does not delete the
-$HOME files, nor does it delete the shared root directory (if enabled). Hence, if you create
+`$HOME` files, nor does it delete the shared root directory (if enabled). Hence, if you create
 a new container having the same shared root, then it will inherit everything installed
 previously. Likewise, if you create the container with the same profile again, then it
-will also have the $HOME as before if you do not explicitly delete the directories
+will also have the `$HOME` as before if you do not explicitly delete the directories
 in `~/.local/share/ybox`.
 
 
@@ -330,10 +330,10 @@ ybox-cmd ybox-arch_apps -- ls -l
 ```
 
 The default profiles also link the .bashrc and starship configuration files from your host
-$HOME directory by default, so you should see the same bash shell configuration as in your
+`$HOME` directory by default, so you should see the same bash shell configuration as in your
 host. These are linked in read-only mode, so if you want to change these auto-linked
 configuration files inside the container, then you will need to create a copy from the symlink
-first (but then it will lose the link from the host $HOME).
+first (but then it will lose the link from the host `$HOME`).
 
 A shell on a container will act like a native Linux distribution environment for most purposes.
 The one prominent missing thing is systemd which is not enabled deliberately since it requires

{ybox-0.9.8.1 → ybox-0.9.9}/src/ybox/__init__.py

@@ -1,2 +1,2 @@
 """`ybox` is a tool to easily manage linux distributions in containers"""
-__version__ = "0.9.8.1"
+__version__ = "0.9.9"

{ybox-0.9.8.1 → ybox-0.9.9/src/ybox.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: ybox
-Version: 0.9.8.1
+Version: 0.9.9
 Summary: Securely run Linux distribution inside a container
 Author-email: Sumedh Wale <sumwale@yahoo.com>, Vishal Rao <vishalrao@gmail.com>
 License: Copyright (c) 2024-2025 Sumedh Wale and contributors
@@ -342,10 +342,10 @@ ybox-destroy ybox-arch_apps
 ```
 
 Will destroy the `apps` container created in the example before. This does not delete the
-$HOME files, nor does it delete the shared root directory (if enabled). Hence, if you create
+`$HOME` files, nor does it delete the shared root directory (if enabled). Hence, if you create
 a new container having the same shared root, then it will inherit everything installed
 previously. Likewise, if you create the container with the same profile again, then it
-will also have the $HOME as before if you do not explicitly delete the directories
+will also have the `$HOME` as before if you do not explicitly delete the directories
 in `~/.local/share/ybox`.
 
 
@@ -374,10 +374,10 @@ ybox-cmd ybox-arch_apps -- ls -l
 ```
 
 The default profiles also link the .bashrc and starship configuration files from your host
-$HOME directory by default, so you should see the same bash shell configuration as in your
+`$HOME` directory by default, so you should see the same bash shell configuration as in your
 host. These are linked in read-only mode, so if you want to change these auto-linked
 configuration files inside the container, then you will need to create a copy from the symlink
-first (but then it will lose the link from the host $HOME).
+first (but then it will lose the link from the host `$HOME`).
 
 A shell on a container will act like a native Linux distribution environment for most purposes.
 The one prominent missing thing is systemd which is not enabled deliberately since it requires