02:48:09funwhilelostHey, guys. I was thinking about trying to package up an app this weekend. One thing I haven't figured out: how do you deal with background work? (I'm looking through Tiny Tiny RSS's package trying to figure this out. I'm assuming it polls feeds.)
05:09:45mnuttgentle nudge to take a look at the pending davros submission…it’s not at all urgent, but I was thinking of posting to HN and it’d be great if it was the newest version :)
05:10:44mnuttassuming the publish actually went through, I’m not 100% sure it did
05:33:39funwhilelostThanks for filing that issue re: background work. I added my comment and subscribed.
11:10:28ocdtrekkieMy home automation experiment turns on and off a light!
11:59:46eternaleyekentonv: Backlogging, you can in fact do tun and then pass the created netdev into a namespace. See "ip link set dev <device> netns <pid>"
12:00:26eternaleyekentonv: So you'd do the dance with /dev/tun, that'd spin up a tunnel netdev, and then you'd assign it to a grain.
20:28:43Jan\ok so, anyone can post a package on the market ?
21:04:15dwrenshaJan\: Anyone can submit a package. It needs to be approved before it will show up.
21:15:57Jan\dwrensha: ok so the package submitter has to maintain that package ?
21:18:03dwrenshawhen you first create a package, you generate a public/private keypair specific to that app. Only a holder of the private key is allowed to push updates to the app.