| 6 Oct 2024 |
 k3rnlp4n1c | Perhaps but i made sure to copy the contents of the original bashrc to my own. | 19:01:49 |
 ﾑ丂ｲ乇尺ﾉ丂ズ | why not try | 19:01:55 |
 jaoheah | * I misread your post, I thought you meant for the pacman.arch part, not the associations | 19:01:56 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | I think order might also matter | 19:02:02 |
| k3rnlp4n1c | No that syntax I definitely get (though its not working for me at the moment). | 19:02:26 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | but yeah you'd have to check ble.sh itself and figure out why bash isn't sourcing blend.sh | 19:03:23 |
| k3rnlp4n1c | I did and it was only referencing its own (host) pacman binary | 19:04:05 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | Problem solved | 19:06:14 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | You can’t associate pacman | 19:06:19 |
| k3rnlp4n1c | Then why put it in the instructions? | 19:07:05 |
| k3rnlp4n1c | The system settings clearly say you can do that | 19:07:24 |
| k3rnlp4n1c | Also I made a backup of the original bashrc before making changes. I don't see any sourcing to a blend.sh | 19:08:59 |
| k3rnlp4n1c | Nor in .bash_profile | 19:09:33 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | ? | 19:14:35 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | I think Rudra put that there | 19:14:45 |
| k3rnlp4n1c | GUI instructions, under associations | 19:14:59 |
| k3rnlp4n1c | Clearly states "we recommend associating package binary names (e.g. pacman, apt, etc) to containers" | 19:15:42 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | 
Download lshDhw1.png | 19:16:01 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | where | 19:16:22 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | I specifically went through to remove pacman assosciation references | 19:16:30 |
| k3rnlp4n1c | 
Download 20241006_141632.jpg | 19:16:53 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | I can't edit that, it's on Rudra's repo, you can PR that out if you want | 19:17:38 |
| ﾑ丂ｲ乇尺ﾉ丂ズ | https://github.com/blend-os/blend/pull/10 | 19:19:59 |
| k3rnlp4n1c | I'll try a brand new install and, without making bashrc changes, I'll test if the prefix.suffix syntax and associations (via the gui or user) work. | 19:28:20 |
| k3rnlp4n1c | Also, info on what directories are mounted unto the guest (besides $HOME) would be nice to be documented for the users. | 19:30:50 |
| k3rnlp4n1c | AFAIK the package and container managemeg wrapping (as well as the .desktop file auto-exportation) is what truly make vanillaOS and BlendOS stand out from the competition hence I really want to see them succeed. | 19:40:43 |
| k3rnlp4n1c | Everyone else is just a read only filesystem with distrobox slapped on top. | 19:41:04 |
| k3rnlp4n1c | * Everyone else in the "immutable" space is just a read only filesystem with distrobox slapped on top. | 19:41:31 |
| k3rnlp4n1c | * AFAIK the package and container management wrapping (as well as the .desktop file auto-exportation) are what truly make vanillaOS and BlendOS stand out from the competition hence I really want to see them succeed. | 19:42:11 |
| k3rnlp4n1c | * Everyone else is just a read only filesystem with distrobox slapped on top. | 19:42:32 |
