someone13574

> @someone13574 This looking pretty good to me. I'll go in and tidy up the manifest details a bit, but otherwise I think this is good to go. > >...

@PgBiel I agree on all the points you made, as well as the potential issue with a flathub submission with this approach, but @ConradIrwin has made it pretty clear that...

> Hello i just try to compile the flatpak and i got this error with this PR > > * cp assets/licenses.md /tmp/tmp.U4vVktxwwM/zed-dev.app/licenses.md > cp: unable to evaluate 'assets/licenses.md': No...

> What's stopping us from running all processes inside the sandbox A good user experience: people expect things (like the terminal) to work. I think I could cut down the...

> It worked out of the box. I guess we have different views of what "out of the box" means in this case. I view "out of the box" as...

You might need to add `archs="x86_64-* aarch64-*"` because those are the only architectures which [wasmtime supports](https://github.com/bytecodealliance/wasmtime/tree/main/cranelift/codegen/src/isa) and it seems that there aren't any easy fixes to allow it to run...

> > I'll see if I can get a PR merge which does this. > > Keep me in touch on that ! Actually, thinking about it some more, cutting...

Shouldn't it wait until Zed is releasing stable builds for linux? They only are shipping [preview builds](https://zed.dev/releases/preview) at the moment.

> looking at the upstream, i see the bundle-linux script bundling something called `cli` > > ```shell > cargo build --release --target "${target_triple}" --package zed --package cli > ``` >...

> would it make sense to `depends="git noto-fonts-ttf"` ? > > If it needs some of the fonts for `do_check`, it probably needs them at runtime too Nope. Zed Mono...