Hi Ronan, hi Joel, Doing a *clean* build of Tizen every day/night is certainly a job for a build farm like OBS. Other large IVI projects I've dealt with have taken that approach. That's not my intention ( though it has the advantage of spotting incorrect dependency and build system info ASAP ).
But I've looked more closely now at the Tizen snapshots, and it appears ( please correct me if I am wrong ) that they are not clean builds - as far as I can see from the dates of the rpms, they are just building the deltas and relying on dependencies. Which is what I would be doing, usually. So yes, in that sense I would just be tracking/duplicating the snapshot process, and if all I was concerned about was having current binaries this would clearly be a pointless duplication of effort. But what I really want is to be sure that I have quick and easy access to the sources for the binaries that are actually in my image. Yes, I could do this retrospectively, and just grab sources for packages on an as-needed basis. But if it's easy to always have all the current sources and binaries ( and I think it is easy, provided build breaks are infrequent - building the daily deltas doesn't normally need a build farm, just a build machine sitting quietly in the corner... ), why would I not do this ? What risks or disadvantages does this approach have compared to your preferred approach ? Cheers, Mark MARK DE ROUSSIER Team Lead Symphony Teleca Sunley House, 46 Jewry Street, Winchester, Hampshire, SO23 8RY Phone: +441962891219, Fax: +441962868867 mailto:[email protected] 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 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
