Hi Joshua, Here is some incomplete info... I hope some other folks can complete this.
- About groups/patterns: we have both patterns and groups defined in our Tizen IVI repository. I'm not 100% sure but I believe the groups as defined in group.xml (e.g. http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/repos/ivi/ia32/packages/repodata/group.xml) are used by MIC when building an image. The patterns can be used within a Tizen IVI image to install a series of packages all at once, e.g. 'zypper in --pattern ivi-applications'. I don't know of any specific way of writing your own pattern/group.xml file other than using a standard XML or text editor. Regarding the various files that can be found under builddata (e.g.: http://download.tizen.org/releases/daily/tizen/ivi/latest/builddata/) - <number>-build.conf: this is the build.conf file that can be used by gbs when doing a local build (see the '-D DIST, --dist DIST' option of 'gbs build --help'). There is some additional info about it at the bottom of this page: https://source.tizen.org/documentation/articles/gbs-build. This is also what's known as the 'prjconf' file in OBS. - build.xml: I don't know about this one - buildlogs: the build log files for every package included in the repository - image-configs.xml: summary of the kickstart files located in image-configs/. I don't know for sure but I suspect it's used by one of our backend tool to generate (or not) an image based on each kickstart file. - image-configs/: where all kickstart files are located (we have slightly different flavours of Tizen IVI images) - manifest/ : the manifest files that can be used by the 'repo' tool. They include all packages that are in the repository (inc. git repository and specific tag that was included in that particular image) Note: these are different than the manifest files you see under images (e.g. http://download.tizen.org/releases/daily/tizen/ivi/latest/images/ivi-mbr-i586/tizen_20130828.7-ivi-mbr-i586.manifest.xml) to the extent that the latter only includes the list of packages that are pre-installed in the image. - reports: it provides some easily readable information about what was recently added/changed in an image compared to previous images. Hope this helps, Geoffroy From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Kim Sent: Thursday, August 29, 2013 1:35 PM To: Chang, Esmond Cc: [email protected] Subject: Re: [TIVI] how to make new package group Thanks Esmond. The pattern.xml is XML file format. Do developers usually edit this file manually? or Is there any tool(except like common XML editor) to edit it? And this file should be located in relative path "repos/ivi/ia32/packages/repodata/patterns.xml"? I want to know the role or usage of files in 'builddata' directory more except 'pattern.xml'. 'tizen_20130729.2_ia32.xml', 'image-configs.xml', 'build.xml' '6438e34cecd63907471b96b6e89a6deb00cc05ce6c5ab6c26bdb0f694f286869-build.conf', etc... Are you experienced building packages or making image for TIVI using by obs-light? If yes, can you explain me the usage examples? 2013/8/29 Chang, Esmond <[email protected]<mailto:[email protected]>> Hi Joshua, TizenIVI package groups are standard and common for image creation. Package groups are defined in the patterns.xml file. Eg: http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/repos/ivi/ia32/packages/repodata/patterns.xml You can define your own package groups in your local repos. Regards, Esmond From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Joshua Kim Sent: Thursday, August 29, 2013 7:30 AM To: [email protected]<mailto:[email protected]> Subject: [TIVI] how to make new package group What should I do to make a new package group(ex. @OEM Apps) in the kickstart file? [kick start files] %packages @Base System @IVI Adaptation @IVI Packaging @IVI Middleware @Wayland @Console Tools @IVI Applications kernel-x86-ivi release-repos -ivi-repos %end And, we can see following directory skeleton in http://download.tizen.org/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/>. How can the 'builddata information' be generated? What software tools do I should use to create it like following data? Could you explain the snapshot release process? [Image removed by sender. [DIR]] builddata/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/> [Image removed by sender. [TXT]] 6438e34cecd63907471b96b6e89a6deb00cc05ce6c5ab6c26bdb0f694f286869-build.conf<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/6438e34cecd63907471b96b6e89a6deb00cc05ce6c5ab6c26bdb0f694f286869-build.conf> [Image removed by sender. [TXT]] build.xml<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/build.xml> [Image removed by sender. [DIR]] buildlogs/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/buildlogs/> [Image removed by sender. [TXT]] image-configs.xml<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/image-configs.xml> [Image removed by sender. [DIR]] image-configs/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/image-configs/> [Image removed by sender. [DIR]] manifest/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/manifest/> [Image removed by sender. [DIR]] reports/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/builddata/reports/> [Image removed by sender. [DIR]] images/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/images/> [Image removed by sender. [DIR]] repos/<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/repos/> -- Joshua Kim ------------------------------------- Leading Research Engineer -- Joshua Kim ------------------------------------- Leading Research Engineer Hyundai Autron Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
<<inline: image001.jpg>>
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
