Hello all,
On Thu, Nov 21, 2013 at 5:30 PM, Hyun-Goo Kang <[email protected]>wrote: > Hi all, > > Let me clarify following situation. > > As I understand, oprofile/valgrind git is for SDK (that’s only reason why > they are in Tizen maintained git) > (1) Valgrind: pre-packaged into SDK (valgrind is a default feature of Tizen > SDK) > > - Installed into emulator/target image on-demand (first connection b/w IDE > & emulator/target) > > (2) Oprofile: pre-loaded in mobile profile image to be used in the SDK > (oprofile support is mandatory feature in Tizen compliance) > > - We are maintaining oprofile git because we want to make its footprint as > small as possible for target. > > > Having an extra package that the emulator can use is fine and why the sdk git tree exists I agree. However I do not think that is the primary usage for those tools. > In summary, the reason why we (SDK domain) are having/maintaining upstream > git in Tizen git is above purpose. > > If someone (mainly platform developers) want to use valgrind, oprofile for > their own use case as following e-mail threads, > > I suggest NOT to use the version of Tizen git, But to use the version of > origin upstream source of valgrind/oprofile. > > Of course, If there is another reason to embed another (additional) > valgrind/oprofile into Tizen maintained git, you can do that under proper > process > > (request/approval by architect group, assigning maintainer for that) > > > The reason for having the upstream git maintained by the platform team is to benefit developers working on system tools for Tizen that can easily be included in images for Tizen developers (I know we have had development images in the past that have included these and other tools by default).
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
