> On Mar 19, 2019, at 8:47 AM, Arjun Salyan via macports-dev > <macports-dev@lists.macports.org> wrote: > > I have some more improvements to demo app: > Build History is now Dynamic: By Making some minor tweaks to the python > script sent by Mojca, I was able to load build history from buildbot into the > database. I loaded only few recent logs for "10.14_x86_64" & "10.13_x86_64". > Since, build history of all ports is not yet on the database, so it would not > appear on port-detail page for all ports. To see it working, gmsh would be a > fine example: https://frozen-falls-98471.herokuapp.com/ports/gmsh/ > <https://frozen-falls-98471.herokuapp.com/ports/gmsh/> . It is not very neat > yet, the os filter is 'just working'. But now we have a good starting point > to improve upon. > Perhaps I’ve missed some previous discussion but please note that we can’t expect all ports to build successfully on the buildbots. There are a number of ports that require a dependency to be installed with a non-default variant in order to build successfully. A short-coming of MacPorts is that this cannot be done progammatically—the user must manually install the dep with the required variant.
An example would be my port, hdhomerun-gui. To function, it requires VLC to be installed with the non-default variant “+DVB”. The buildbot cannot successfully built this port because there is no user to manually install VLC +DVB. My search found 195 Portfiles that include the active_variants PortGroup. Not all of them will fail to build—the port may be testing if a dep is installed with an unsupported non-default variant. I think that is rather less common but I didn’t review every case. When this is rolled out, we don’t want to make users think that a port will fail to build on their system when it is just a case of needing a non-default variant. However, I don’t know how to handle this cleanly. Perhaps we could parse the build log looking for the message that informs the user how to install the required variant. If found, instead of saying the build failed, we could indicate that the build was not attempted as the buildbot configuration could not support a successful install. Craig
