On Thu, Jul 18, 2019 at 02:20:34PM +0200, Andrea Bolognani wrote: > The libosinfo project would like to start using these container > images in their own CI pipeline, so they need the corresponding > build dependencies to be included. > > Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> > --- > refresh | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/refresh b/refresh > index 81df77e..2491613 100755 > --- a/refresh > +++ b/refresh > @@ -59,13 +59,18 @@ class Dockerfile: > self.cross_arch = None > > self.projects = [ > + "libosinfo", > "libvirt", > + "osinfo-db", > + "osinfo-db-tools", > ] We get away with this single container for libosinfo we don't have any dependancies between components. It doesn't work in general though. ie the build deps for libvirt-perl skip 'libvirt' because they assume we already chain built libvirt in the CI. This doesn't happen except in Jenkins CI though. We've never created a solution for fully populating deps such that the system is self-contained and doesn't need to chain build other projects first. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
