On Thu, 12 Sep, 2019 at 22:39, Philip Withnall <phi...@tecnocode.co.uk>
wrote:
On Thu, 2019-09-12 at 19:14 +0100, Emmanuele Bassi wrote:
On Thu, 12 Sep, 2019 at 19:08, Philip Withnall
<phi...@tecnocode.co.uk> wrote:
That sounds like something people are going to forget to do. Would
it be possible to use computers to automate this?
It's software: anything is possible.
As to whether we can automate this **right now**, the answer is: no.
It's a shame that build deps can't be picked up automatically from the
meson build config, where it's already specified.
What about requiring modules include a buildstream config fragment with
a well-known name in their repos, much like how DOAP files are
required, which then gets pulled in by the release team's CI?
That would also enable having a standard Gitlab CI script for the
per-module CI which also pulls the config in and does a build based on
that (much like the one that already exists for for building Flatpak
manifest), and hence also act as a reminder for maintainers to keep it
up to date when it fails.
//Mike
--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list