OK, now I understand. The concern is not so much with the approach per se, as that the particular tool involved is not trusted for this purpose. Fair enough, that's very good to know.
But the 'OBS vs GBS' situation does trouble me a lot, for reasons I'm finding hard to explain. When I've worked in other environments where build farms have been used, then in general they have just been a way to more quickly process the same build scripts that I could otherwise run on my local system. There is some additional metadata and script wrappers required, but this is for managing the build farm. It does not alter dependency relationships, or build targets and their associated configuration info, and it's always possible to do exactly the same build using your local system as the farm is doing, provided you know the config, or perhaps just the target. So let me try to pin this down. Are you claiming that gbs ( used with default options to build a particular package locally ) does not guarantee to produce the same binary as OBS does due to config differences ? Or that gbs, when used to build many packages, does not handle dependencies very well ? The second of these is unfortunate, but I'm afraid the first would encourage me to take control of the whole build, rather than mixing OBS and gbs outputs i.e. components built with different configs. Cheers, Mark MARK DE ROUSSIER Team Lead Symphony Teleca Sunley House, 46 Jewry Street, Winchester, Hampshire, SO23 8RY Phone: +441962891219, Fax: +441962868867 [email protected]<mailto:[email protected]> www.symphonyteleca.com<http://www.symphonyteleca.com> Teleca Limited, a company registered in England & Wales, registration number 2773878, registered office at Sunley House, 46 Jewry Street, Winchester, Hampshire SO23 8RY. VAT registration number GB 674 6583 90 Follow what's going on at Symphony Teleca's blog on www.symphonyteleca.com/blog<http://www.symphonyteleca.com/blog>. Please consider the environment before you print. Notice to recipient: This e-mail (including any attachments) is meant for the intended recipient only, may contain confidential and proprietary information, and is protected by law. If you received this e-mail in error, please immediately notify the sender of the error by return e-mail, delete this communication and any attachments, and shred any printouts. Unauthorized review, use, dissemination, distribution, copying or taking of any action based on this communication is strictly prohibited.
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
