[04:05] <brlin> https://forum.snapcraft.io/t/reliable-way-of-detecting-snap-confinement-mode/8896
[04:06] <brlin> zyga: ack
[04:07] <brlin> BTW, I'm referring to --classic snaps, but installed with with --jailmode switch
[04:07] <brlin> s/with with/with the/
[05:22] <brlin> https://bugs.launchpad.net/snapcraft/+bug/1807553
[05:22] <mup> Bug #1807553: Snapcraft crashes after changing `dump` part's source content <Snapcraft:New> <https://launchpad.net/bugs/1807553>
[06:39] <brlin> https://bugs.launchpad.net/snapcraft/+bug/1807555
[06:39] <mup> Bug #1807555: Snapcraft forgot adopt-info is provided by `snapcraft set-version` in some circumstances <Snapcraft:New> <https://launchpad.net/bugs/1807555>
[08:40] <xieta> Hello, I am new to snapcraft and while working to make a snap for an altcoin, ran into this issue: https://forum.snapcraft.io/t/access-to-specific-hidden-file-path-in-users-home/6948 Is there still no interface to read and write to specified hidden directories?
[10:13] <brlin> xieta: I posted a workaround, refer to the forum post
[10:59] <xieta> brlin, okay thanks. Am I reading this right that the user will need to make a hard link for each revision?
[10:59] <xieta> or will that hard link just get copied into the next revision?
[11:54] <brlin> xieta: Unless you can redirect the config file to SNAP_DATA_COMMON, you have to prompt user to hardlink it on every refresh
[11:55] <xieta> Thanks for the work around and response.
[11:56] <brlin> s/SNAP_DATA_COMMON/SNAP_USER_COMMON/
[11:57] <xieta> In this case it is more of a whole data directory rather than just a config file.
[11:58] <brlin> My assumption is the hardlink trick works with directories as well, but not tested
[11:59] <brlin> ln: .config: hard link not allowed for directory
[11:59] <brlin> nevermind...
[11:59] <xieta> I'm not sure if you're familiar with how Bitcoin or other altcoins store their data directory and wallet file, but that's exactly the use case I'm looking at snap for and it seems like snap would be perfect for making just another node to add to the network backbone connectivity -- (because then I don't have to worry about the original hidden directory)
[11:59] <brlin> For directories you have to use bind mount instead
[12:00] <xieta>  - you know how there are choices to make with any implementation. Basically in this case its a toss-up between changing the default data directory to not be a hidden directory - or not using snap for financial data applications.
[12:00]  * xieta is still mulling it over.
[12:01] <xieta> The guy who asked me to look into snapcraft probably just wants a snap made to grow the network and not necessarily to hold a wallet. So if that's what he tells me as a stakeholder (waiting for his response) then this should be a nifty snap and I won't have to do any tricks with the hidden files or directories.