Hi,
On 06/05/16 00:02, Nikita Karetnikov wrote:
> Has anyone packaged something like this? What's a proper way to solve this
> without compromising the integrity of a system (think of potential security
> issues or just proper operation)?
There is no way to solve this. Packages with ad hoc
I suggest you look into the way Steam is packaged, as it also self-
updates (and updates other applications under its control).
On Fri, May 6, 2016, at 09:13 AM, Tomasz Czyż wrote:
> IMHO, this is pretty simple.
> You pack "first/original" version into immutable store /nix/store. You
> add
IMHO, this is pretty simple.
You pack "first/original" version into immutable store /nix/store. You add
tiny wrapper around it, which checks if /var/lib/ exists, if not,
create directory and copy binary there and run it there. If file already
exists in /var/lib, execute it directly. Application
On Fri, May 06, 2016 at 01:02:15AM +0300, Nikita Karetnikov wrote:
> The server is controlled by other people.
I'd like to add that I'm assuming that these people are not malicious. In this
case, I'm more worried about a misconfigured package that might break my system
in some way.
I've talked a bit about this on IRC earlier today, but I think the issue
deserves an in-depth discussion. It's more of a general policy question, a
clash of an imperative world and a pure functional one. I'm trying to package a
Java program, a client, which can be (among other things) updated by
