| *** bochecha has joined #buildstream | 00:20 | |
| *** bochecha has quit IRC | 00:52 | |
| *** bochecha has joined #buildstream | 01:30 | |
| *** bochecha has quit IRC | 02:02 | |
| *** bochecha has joined #buildstream | 02:21 | |
| *** bochecha has quit IRC | 02:53 | |
| *** bochecha has joined #buildstream | 03:01 | |
| *** bochecha has quit IRC | 03:52 | |
| *** bochecha has joined #buildstream | 04:03 | |
| *** bochecha has quit IRC | 05:20 | |
| *** palasso has joined #buildstream | 05:23 | |
| *** bochecha has joined #buildstream | 05:40 | |
| *** bochecha has quit IRC | 06:12 | |
| *** bochecha has joined #buildstream | 06:20 | |
| *** juergbi has quit IRC | 06:51 | |
| *** juergbi has joined #buildstream | 06:51 | |
| *** tristan has quit IRC | 07:15 | |
| *** tristan has joined #buildstream | 08:59 | |
| *** ChanServ sets mode: +o tristan | 08:59 | |
| bochecha | hi, I'm still trying to produce an ostree repo out of my buildstream build pipeline: a repo that contains a tree with the installed built artifacts, and which could be checked out and deployed on a server | 09:18 |
|---|---|---|
| bochecha | tristan, juergbi: I was told yesterday that one of you might be able to help? :) | 09:18 |
| juergbi | hi bochecha, we don't yet support output to a user-specified ostree. we definitely want this, though, will be useful for flatpak, among other things | 09:28 |
| juergbi | right now you have to manually/separately checkout the result with 'bst checkout' and then commit this to an ostree repo | 09:28 |
| bochecha | alright, I can do that for now :) | 09:29 |
| juergbi | we will likely add support for tar export (like git archive) to buildstream core. ostree export support might then be built on top of tar stream export (ostree has tar import support) or directly as a plugin | 09:30 |
| tristan | We were talking about having a tarball option to `bst checkout`, and since ostree has a way to read a tar stream (I think ?) this should be good enough to just pipe into an ostree commit command | 09:30 |
| tristan | right | 09:30 |
| juergbi | :) | 09:30 |
| bochecha | I'm investigating BuildStream for Libraries Without Borders, we'd like to move away from building a big Debian package (with all the dependencies inside) to building an OSTree repo, so that clients can have static-deltas and other nice OSTree features | 09:30 |
| bochecha | at the same time, the artifacts caching of BuildStream makes me ♥_♥ | 09:31 |
| juergbi | bochecha: have you considered flatpak? | 09:32 |
| bochecha | juergbi: I have | 09:33 |
| bochecha | juergbi: but we're doing web apps | 09:33 |
| juergbi | ah ok | 09:33 |
| bochecha | I talked with alex about it, and that's not a use-case he wants to support in Flatpak (at least not in the short to medium term) | 09:33 |
| juergbi | yes, don't know how easily flatpak could be generalized | 09:33 |
| juergbi | it could be interesting to support flatpak for more than just desktop apps | 09:34 |
| bochecha | which makes sense of course, flatpak is great at what it does specifically because it has a tight focus on desktop apps :) | 09:34 |
| juergbi | yes, if it added too much complexity, it would be better to keep it focused and possibly develop a separate tool for other use cases | 09:34 |
| bochecha | for now, after playing with it for a few days, I'm starting to feel confident that BuildStream could really help us | 09:35 |
| juergbi | great | 09:36 |
| bochecha | we might have to develop some small tooling around it for our specific use-cases (that remains to be seen, I'd need to manage to build a complete thing), but that could just be wrapper to make things nicer, BuildStream seems to provide the fundamentals already :) | 09:36 |
| tristan | I dont know how you want to deploy but I expect it will be fairly simple to writeup a docker deployment element, was hoping to cook one up last week but ran out of time | 09:37 |
| tristan | (that and, I just dont know enough about docker myself) | 09:37 |
| tristan | bochecha, you might also be interested in looking at https://gitlab.com/BuildStream/debootstrap-ostree/... which is basically just a silly little script which will turn debian into a revisioned ostree base runtime | 09:39 |
| bochecha | tristan: I have looked at it :) | 09:39 |
| bochecha | I'm doing the same but with a Fedora 26 base (because Python 3.6) | 09:40 |
| *** tlater has joined #buildstream | 09:42 | |
| tristan | bochecha, I'll be away for 2 weeks vacation (but will stop into irc at least a few times a week I expect) and juergbi will be around in that time; just let us know if you need a hand figuring anything out :) | 09:44 |
| tristan | And if you just so happen to writeup a docker deployment element (hint: could be a derivative of ScriptElement), then we want one ! :D | 09:45 |
| tristan | but one will probably appear soon anyway :) | 09:46 |
| bochecha | tristan: we want use docker | 09:46 |
| bochecha | sorry | 09:46 |
| bochecha | I mean we **won't** use docker | 09:46 |
| tristan | Ah sure, so you want to deploy a bootable system image ? | 09:47 |
| tristan | Those are a bit more tricky | 09:47 |
| tristan | cause anyway, bootloader and image partitioning and such | 09:47 |
| bochecha | no, not a bootable system image | 09:48 |
| bochecha | just an ostree repo, with a checkout on the server | 09:48 |
| bochecha | and then bubblewrap to run the thing | 09:48 |
| tristan | Ah so something fairly custom :) | 09:48 |
| tristan | Sure | 09:48 |
| bochecha | yeah, we deploy on some very low-performance ARM boards, and last time we had tested Docker had more overhead than Bubblewrap | 09:49 |
| bochecha | OSTree also allows downloading less stuff than Docker's layer systems, which is a very desirable property for us (some boxes have extremely bad Internet access, we deploy in refugee camps and war zones) | 09:50 |
| gitlab-br-bot | push on buildstream@cross_platform (by Tristan Maat): 1 commit (last: platform.py: Fix typo) https://gitlab.com/BuildStream/buildstream/commit/37f2c84945d35b8b7e6e683334d0d7f829a2316e | 09:57 |
| gitlab-br-bot | push on buildstream@cross_platform (by Tristan Maat): 1 commit (last: _sandboxchroot.py: Fix platform) https://gitlab.com/BuildStream/buildstream/commit/8b37644ac9cddaabe65aa7ec7c7ac0c9d1f27b3e | 10:09 |
| gitlab-br-bot | push on buildstream@cross_platform (by Tristan Maat): 1 commit (last: _sandboxbwrap: Make psutil not a strict dependency) https://gitlab.com/BuildStream/buildstream/commit/0940710cf44954c646cbc30b6bcc58009d00a09a | 11:15 |
| gitlab-br-bot | push on buildstream@cross_platform (by Tristan Maat): 1 commit (last: _sandboxbwrap: Make psutil not a strict dependency) https://gitlab.com/BuildStream/buildstream/commit/f309fadac4686e4fd6b1c420290131974d6c547d | 11:18 |
| gitlab-br-bot | push on buildstream@cross_platform (by Tristan Maat): 1 commit (last: _sandboxbwrap: Make psutil not a strict dependency) https://gitlab.com/BuildStream/buildstream/commit/fde68af8cbcfa8960d276852ffa292331aea0939 | 11:21 |
| *** tlater has quit IRC | 11:31 | |
| bochecha | could BuildStream automatically add ".bst" to the CLI arguments representing targets? | 11:51 |
| bochecha | I keep forgetting to type it ^_^ | 11:51 |
| juergbi | may be worth considering. at the very least we should create a bash completion helper | 12:00 |
| *** tlater has joined #buildstream | 12:03 | |
| bochecha | yeah, bash completion would be great, but it probably won't work when installing buildstream from git with `pip --user` | 12:07 |
| tlater | It's possible according to the bash-completion FAQ | 12:33 |
| tlater | Though I'm not sure if it would actually load | 12:33 |
| bochecha | yeah, I guess you'd have to explicitly load the completion file where it is installed, from your bashrc | 12:34 |
| tlater | It *should*, if you install to the directory specified by `pkg-config --variable=completionsdir bash-completion` | 12:35 |
| tlater | But user installs are an edge case for which that probably isn't actually something sensible | 12:35 |
| bochecha | exactly | 12:36 |
| bochecha | I'm happy to wait for bash-completion until BuildStream gets to the point where distro packages start making sense :) | 12:36 |
| *** igor has quit IRC | 12:41 | |
| *** anahuelamo_ has quit IRC | 12:50 | |
| *** anahuelamo has joined #buildstream | 12:52 | |
| gitlab-br-bot | push on buildstream@cross_platform (by Tristan Maat): 2 commits (last: Add platform.switch function) https://gitlab.com/BuildStream/buildstream/commit/3f5ff2433350f06ec7822a9ecd6fc15de3d16ff2 | 13:54 |
| *** tlater has left #buildstream | 14:19 | |
| gitlab-br-bot | buildstream: issue #59 ("`bst source-bundle` doesn't work") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/59 | 15:32 |
| gitlab-br-bot | buildstream: issue #60 ("Status message when doing cache network operations") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/60 | 15:40 |
| gitlab-br-bot | buildstream: issue #61 ("Add `all` value to depends `type`") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/61 | 15:45 |
| *** tristan has quit IRC | 16:00 | |
| gitlab-br-bot | buildstream: issue #62 ("Extend the `tar` source plugin to include `etag` support") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/62 | 16:01 |
| *** tristan has joined #buildstream | 16:29 | |
| *** bochecha has quit IRC | 16:58 | |
| *** tristan has quit IRC | 17:06 | |
| *** tiagogomes has quit IRC | 17:55 | |
| *** tristan has joined #buildstream | 21:04 | |
| *** palasso has quit IRC | 21:12 | |
| *** palasso has joined #buildstream | 21:50 | |
| *** palasso has quit IRC | 22:23 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!