*** Prince781 has quit IRC | 00:12 | |
*** zalupik has joined #buildstream | 00:27 | |
*** Prince781 has joined #buildstream | 01:05 | |
*** Prince781 has quit IRC | 01:28 | |
*** Prince781 has joined #buildstream | 01:31 | |
*** Prince781 has quit IRC | 01:53 | |
*** Prince781 has joined #buildstream | 02:09 | |
*** Prince781 has quit IRC | 02:56 | |
*** Prince781 has joined #buildstream | 02:58 | |
*** Prince781 has quit IRC | 03:10 | |
*** slaf has quit IRC | 03:24 | |
*** slaf has joined #buildstream | 03:39 | |
*** tristan has joined #buildstream | 08:04 | |
*** dominic has joined #buildstream | 08:48 | |
*** tiago has joined #buildstream | 08:54 | |
*** toscalix has joined #buildstream | 09:11 | |
*** jonathanmaw has joined #buildstream | 10:04 | |
*** ssam2 has joined #buildstream | 10:05 | |
gitlab-br-bot | buildstream: issue #254 ("Strict rebuild needs to be a dependency semantic") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/254 | 10:45 |
---|---|---|
gitlab-br-bot | buildstream: issue #255 ("Document sandbox/artifact cache limitations") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/255 | 11:56 |
tristan | ssam2, 255 above is documenting limitations btw | 11:56 |
tristan | juergbi, another random thought that still hasnt been mapped which occurred to me the other day... | 12:11 |
tristan | juergbi, there may be some security concerns to deal with for running user provided python plugins on open build servers (think: flathub) | 12:12 |
tristan | this might be moot, though | 12:12 |
tristan | I suppose that I might be able to demonstrate right now, that I can upload a flatpak json file and have that pull a git module and "build it", where the Makefile ends up mining my bitcoins... | 12:13 |
ssam2 | thanks tristan | 12:18 |
*** tristan has quit IRC | 12:19 | |
ssam2 | its a good point, a public buildstream server would probably want to disallow or require human reviews for custom plugins | 12:20 |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 12:23 |
juergbi | yes, interesting point | 12:41 |
persia | But not unique to the tooling : same could be done with github + travisci, or *any* remote execution tool that depends on provided source code (of which there are many provided at low or zero cost for free software). | 12:47 |
gitlab-br-bot | buildstream: issue #256 ("Allow downloading sources as individual files straight into the build tree") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/256 | 12:48 |
gitlab-br-bot | buildstream: issue #256 ("Allow downloading sources as individual files straight into the build tree") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/256 | 13:06 |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 13:42 |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 14:22 |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 14:51 |
*** bethw has joined #buildstream | 15:07 | |
*** noisecell has quit IRC | 15:14 | |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 15:24 |
*** juergbi has quit IRC | 15:24 | |
*** juergbi has joined #buildstream | 15:25 | |
juergbi | jonathanmaw: one thing i'm wondering about regarding #214 is whether we would also need more control of indirect dependencies | 15:53 |
juergbi | i.e., if i only depend on one part of another element, do i still want to pull in all its runtime dependencies? | 15:54 |
jonathanmaw | juergbi: I can see if you've decided to omit the locale split from your dependency, you'd not be interested in the locale of indirect dependencies | 15:56 |
jonathanmaw | But I can see cases when we're using split domains in ways other than the buildstream default (dpkg elements, for example), and we probably wouldn't want to say "use only these split domains" for their dependencies | 15:57 |
juergbi | right, that's what came to mind | 15:58 |
juergbi | but we should probably keep the focus on how split domains are supposed to be used | 15:58 |
juergbi | i want to make sure we clearly understand the scope of the use cases | 15:59 |
juergbi | jonathanmaw: are you aware of any use cases besides the autotools auto-detection one? | 15:59 |
jonathanmaw | juergbi: I'm not sure, really. I don't really have a concrete real-world example of the autotools auto-detection to test against, either :/ | 16:00 |
*** noisecell has joined #buildstream | 16:01 | |
juergbi | afaict, it would only help the autotools use case if split domains were used to split something in a dpkg-style, not like usual buildstream split domains | 16:01 |
juergbi | e.g., splitting library from binary | 16:01 |
juergbi | well, devel is sufficient | 16:01 |
jonathanmaw | yeah, I think "devel" and "runtime" split domains are enough to separate library from binary | 16:02 |
juergbi | if all elements consistently exclude devel from the runtime dependency, the proposed approach should help, yes | 16:03 |
juergbi | however, it seems relatively cumbersome having to annotate this everywhere, tbh | 16:03 |
juergbi | just so that you can avoid adding an explicit option to the autotools project (which would likely be accepted upstream if that wasn't supported yet) | 16:04 |
juergbi | with buildstream split domains, i'm wondering whether it wouldn't make more sense to have some project-wide configuration that 'devel' should never be included in runtime dependencies | 16:05 |
juergbi | instead of having to declare this everywhere | 16:05 |
*** noisecell has quit IRC | 16:06 | |
juergbi | maybe that's not flexible enough | 16:06 |
persia | There are cases in Debian where -devel packages are runtime dependencies. | 16:09 |
juergbi | interesting | 16:10 |
juergbi | we probably would still want element-specific override possibilities even if we had global support | 16:10 |
persia | Two classes are common: the first being certain packages that have development-specific tooling required to use the development content | 16:10 |
persia | The second being header packages that depend on that class of tooling | 16:10 |
persia | There are some additional corner cases, but if we can handle those two, we're in decent shape. | 16:11 |
juergbi | jonathanmaw: with your proposal could we list the same filename twice as a dependency, once as build dependency with all split domains and once as runtime dependency only with the 'runtime' split domain? i would expect that to be a common pattern | 16:11 |
juergbi | (but again, sounds cumbersome to do this everywhere) | 16:11 |
jonathanmaw | juergbi: with this proposal, it stages the union of all the split domains found while traversing the dependencies. Since the build dependency on all split domains is a build dependency, it won't show up for an indirect dependency, aiui. | 16:14 |
jonathanmaw | but if we runtime depend on it with the "runtime" split domain, that'll show up with later indirect dependencies. | 16:14 |
jonathanmaw | i.e. all the domains just once, but just "runtime" every time it's an indirect dependency | 16:15 |
jonathanmaw | though tbh my understanding of the dependency tree feels a lot shakier than it ought to be if I'm going to be changing how it works :/ | 16:16 |
*** Prince781 has joined #buildstream | 16:18 | |
gitlab-br-bot | buildstream: merge request (sam/plugin-error->master: _plugincontext.py: Fix unhandled exception if plugin is not found) #274 changed state ("merged"): https://gitlab.com/BuildStream/buildstream/merge_requests/274 | 16:18 |
*** ernestask has joined #buildstream | 16:24 | |
gitlab-br-bot | buildstream: merge request (modAndTest->master: Making changes to various documents:) #206 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/206 | 16:31 |
gitlab-br-bot | buildstream: merge request (postbuild->master: Added Postbuild documentation) #236 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/236 | 16:32 |
*** toscalix has quit IRC | 16:33 | |
gitlab-br-bot | buildstream: merge request (createProject->master: Adding create project document) #237 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/237 | 16:33 |
gitlab-br-bot | buildstream: merge request (buildproject->master: Added buildproject doc) #238 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/238 | 16:34 |
gitlab-br-bot | buildstream: merge request (modAndTest->master: Making changes to various documents:) #206 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/206 | 16:36 |
juergbi | nexus: i still see the 'Specify wrong value type' comment in the latest version. i can remove this locally, no problem, just want to make sure you don't have any local changes that you forgot to push | 16:41 |
gitlab-br-bot | buildstream: merge request (modAndTest->master: Making changes to various documents:) #206 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/206 | 16:42 |
nexus | juergbi: hmm, i removed that, 1 min | 16:43 |
nexus | yup, didnt push | 16:44 |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 16:44 |
juergbi | nexus: a small hint about commit messages: the main purpose is to describe the reasoning behind the change. i.e., don't need to describe the details of what you've changed that are easily visible in the diff itself, rather describe for example what was broken before | 16:44 |
juergbi | ok, ta | 16:44 |
gitlab-br-bot | buildstream: merge request (modAndTest->master: Making changes to various documents:) #206 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/206 | 16:47 |
jmac | Are BST environment variables (like BST_PROFILE) intentionally undocumented? | 16:51 |
ltu | nexus, i read a good article on commit messages recently - https://chris.beams.io/posts/git-commit/ | 16:51 |
ssam2 | jmac, I didn't know that even existed | 16:52 |
ssam2 | we should mention it in HACKING.md | 16:53 |
ssam2 | https://gitlab.com/BuildStream/buildstream/issues/206 is kind of related | 16:53 |
jmac | ssam2: OK | 16:55 |
jmac | BST_PROFILE does profiling using the cProfile module, but it's not really the sort of information we want for our performance work right now | 16:56 |
*** mcatanzaro has joined #buildstream | 16:59 | |
gitlab-br-bot | buildstream: merge request (modAndTest->master: Making changes to various documents:) #206 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/206 | 17:06 |
gitlab-br-bot | buildstream: issue #243 ("dpkg import source plugin") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/243 | 17:09 |
gitlab-br-bot | buildstream: merge request (postbuild->master: Added Postbuild documentation) #236 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/236 | 17:12 |
gitlab-br-bot | buildstream: issue #166 ("bst sometimes modifies source `track` parameters") changed state ("closed") https://gitlab.com/BuildStream/buildstream/issues/166 | 17:14 |
gitlab-br-bot | buildstream: merge request (issue-166_yaml_removing_underscores->master: Issue #166 yaml removing underscores) #245 changed state ("closed"): https://gitlab.com/BuildStream/buildstream/merge_requests/245 | 17:14 |
gitlab-br-bot | buildstream: merge request (postbuild->master: Added Postbuild documentation) #236 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/236 | 17:17 |
gitlab-br-bot | buildstream: merge request (postbuild->master: Added Postbuild documentation) #236 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/236 | 17:22 |
nexus | is the gitlab down? | 17:23 |
jmac | gitlab.com looks ok to me | 17:24 |
nexus | hmm | 17:24 |
nexus | i'll restart my browser | 17:24 |
ssam2 | i got a temporary error recently | 17:25 |
nexus | maybe it's got load issues | 17:25 |
nexus | kk back up | 17:27 |
nexus | i'm getting some issues with one of my docs, it's giving me an error about my label not proceeding a section header, but as far as i can tell, it is | 17:28 |
gitlab-br-bot | buildstream: merge request (postbuild->master: Added Postbuild documentation) #236 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/236 | 17:32 |
gitlab-br-bot | buildstream: merge request (jmac/microsecond-timing->master: Optional microsecond timing for log messages) #275 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/275 | 17:35 |
nexus | grrrr | 17:36 |
jmac | Did my merge request anger you? | 17:37 |
nexus | no, mine did | 17:40 |
gitlab-br-bot | buildstream: merge request (createProject->master: Adding create project document) #237 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/237 | 17:41 |
nexus | juergbi: Is there anything elsethat needs to be done with my docs btw, or are they okay to be merged? | 17:42 |
juergbi | nexus: afaik, tristan is planning to look at these MRs as he has already looked at least at some of them before and he has a clear idea how he wants the doc to be structured | 17:44 |
gitlab-br-bot | buildstream: issue #256 ("bst should not run autogen or autoreconf for autotools tarballs") changed state ("opened") https://gitlab.com/BuildStream/buildstream/issues/256 | 17:44 |
gitlab-br-bot | buildstream: merge request (jmac/microsecond-timing->master: WIP: Optional microsecond timing for log messages) #275 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/275 | 17:44 |
jmac | Oops, forgot the WIP | 17:45 |
gitlab-br-bot | buildstream: merge request (createProject->master: Adding create project document) #237 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/237 | 17:45 |
nexus | juergbi: ok, they just seemed to be among the last unmerged MRs and i wnated to know if i needed to change anything. They SHOULD all be ready to be merged now, i've been sorting out any CLI errors i could find | 17:46 |
gitlab-br-bot | buildstream: merge request (createProject->master: Adding create project document) #237 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/237 | 17:50 |
*** Prince781 has quit IRC | 18:16 | |
jmac | How can I stop bst from downloading prebuilt artifacts? I've deleted ~/.cache/buildstream and removed the 'artifacts' field from project.conf. | 18:17 |
gitlab-br-bot | buildstream: merge request (sam/233-push-after-pull->master: Avoid pushing things we just pulled) #276 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/276 | 18:19 |
ssam2 | jmac, deleting the artifacts field from project.conf should do the trick | 18:19 |
ssam2 | unless you have another cache configured in ~/.config/buildstream.conf | 18:20 |
jmac | Nope, no ~/.config at all | 18:21 |
ssam2 | ok, i have no idea how it could be pulling stuff then | 18:21 |
ssam2 | is there a junction element importing a different project ? | 18:22 |
jmac | Yep, that was it | 18:24 |
*** ssam2 has quit IRC | 18:27 | |
*** Prince781 has joined #buildstream | 18:39 | |
*** persia has quit IRC | 18:39 | |
gitlab-br-bot | buildstream: merge request (jmac/microsecond-timing->master: WIP: Optional microsecond timing for log messages) #275 changed state ("opened"): https://gitlab.com/BuildStream/buildstream/merge_requests/275 | 18:42 |
* paulsherwood wonders what is the use-case for microsecond timing | 18:44 | |
jmac | It's for performance analysis. I'd like to be able to produce a report on how long fetching and building takes for a large project | 18:45 |
jmac | There's no real need for it to be any more precise than milliseconds, but Python provides microseconds | 18:49 |
*** dominic has quit IRC | 18:49 | |
*** jonathanmaw has quit IRC | 18:57 | |
paulsherwood | ack :) | 18:58 |
*** tristan has joined #buildstream | 19:35 | |
*** noisecell has joined #buildstream | 20:02 | |
*** Prince781 has quit IRC | 20:03 | |
*** noisecell has quit IRC | 20:03 | |
*** Prince781 has joined #buildstream | 20:15 | |
*** valentind has joined #buildstream | 20:55 | |
*** Prince781 has quit IRC | 21:32 | |
*** tiago has quit IRC | 21:40 | |
*** ernestask has quit IRC | 21:41 | |
*** Prince781 has joined #buildstream | 21:50 | |
*** Prince781 has quit IRC | 22:12 | |
*** Prince781 has joined #buildstream | 22:18 | |
*** aday has quit IRC | 22:23 | |
*** valentind has quit IRC | 22:57 | |
*** Prince781 has quit IRC | 23:04 | |
*** Prince781 has joined #buildstream | 23:19 | |
*** mcatanzaro has quit IRC | 23:49 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!