summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2018-12-04Fix build errortizen_5.5.m2_releasesubmit/tizen_5.5_wearable_hotfix/20201026.184307submit/tizen_5.5_mobile_hotfix/20201026.185107submit/tizen_5.5/20191031.000007submit/tizen/20181204.104738accepted/tizen/unified/20181205.063326accepted/tizen/5.5/unified/wearable/hotfix/20201027.100926accepted/tizen/5.5/unified/mobile/hotfix/20201027.074601accepted/tizen/5.5/unified/20191031.012345tizen_5.5_wearable_hotfixtizen_5.5_tvtizen_5.5_mobile_hotfixtizen_5.5accepted/tizen_5.5_unified_wearable_hotfixaccepted/tizen_5.5_unified_mobile_hotfixaccepted/tizen_5.5_unifiedDongkyun Son1-1/+1
Some #directives are missing their corresponding #end ___ tag: if Change-Id: I044cdc347c2db990dbc597dcc42a5d1589291fee Signed-off-by: Dongkyun Son <dongkyun.s@samsung.com>
2018-12-04Add condition for %env section backward compatibilitysubmit/tizen/20181204.094226Slava Barinov2-1/+4
Change-Id: I5281f4ec6359f0e3f582ad1cfc6939da4ff134a3 Signed-off-by: Slava Barinov <v.barinov@samsung.com>
2018-11-30Add support for %env sectionsubmit/tizen/20181130.063616Slava Barinov2-1/+16
Env-scripts support are required for building certain firmware configurations, e.g. sanitized firmwares and can be used for setting up environment variables for firmware build. Change-Id: I95b3443132fd7087728cd257da7f84dc0aee1677 Signed-off-by: Slava Barinov <v.barinov@samsung.com> Signed-off-by: Dongkyun Son <dongkyun.s@samsung.com>
2017-11-10Add possibility to parse list of partition filessubmit/tizen_5.0/20181101.000006submit/tizen/20171129.080753accepted/tizen/unified/20171130.063430accepted/tizen/5.0/unified/20181102.025509Katarzyna Gorska1-3/+13
Kickstarter was not able to correctly parse config files that contained a list of partition files in "Part" section. Now it is possible to add several partition files in that section. Change-Id: Idcb22bd6bcb17061b9c7b5af8dea222283216e2c Signed-off-by: Katarzyna Gorska <k.gorska@samsung.com>
2017-08-24Add 'Runscript' templete which support script running between 'each img ↵submit/tizen/20170824.111954accepted/tizen/unified/20170825.043947SoonKyu Park2-1/+17
creation' and 'tar.gz creation' Image creation order : Create *.img, *.bin - Runscript - Create xxxx.tar.gz Change-Id: Ia77c05072283ca8cde5b95a127a0cbb28c8edba7
2016-08-30Do not print timestamp in python-Cheeta by setting an argument.tizen_4.0.m1_releasesubmit/tizen_unified/20170308.100413submit/tizen_4.0/20170828.100006submit/tizen_4.0/20170811.094300submit/tizen_3.0_wearable/20161015.000003submit/tizen_3.0_tv/20161015.000002submit/tizen_3.0_mobile/20161015.000003submit/tizen_3.0_ivi/20161010.000003submit/tizen_3.0_common/20161104.104000submit/tizen_3.0.m2/20170104.093752submit/tizen/20160921.004331submit/tizen/20160913.071022accepted/tizen/wearable/20160921.232905accepted/tizen/unified/20170309.035902accepted/tizen/tv/20160921.232920accepted/tizen/mobile/20160921.232912accepted/tizen/ivi/20160921.232926accepted/tizen/common/20160913.170436accepted/tizen/4.0/unified/20170828.222950accepted/tizen/4.0/unified/20170816.013948accepted/tizen/3.0/wearable/20161015.083244accepted/tizen/3.0/tv/20161016.004709accepted/tizen/3.0/mobile/20161015.033522accepted/tizen/3.0/ivi/20161011.044345accepted/tizen/3.0/common/20161114.110907accepted/tizen/3.0.m2/wearable/20170104.143831accepted/tizen/3.0.m2/tv/20170104.143435accepted/tizen/3.0.m2/mobile/20170104.142939tizen_3.0_tvtizen_3.0.m2accepted/tizen_wearableaccepted/tizen_tvaccepted/tizen_mobileaccepted/tizen_iviaccepted/tizen_commonaccepted/tizen_3.0.m2_wearableaccepted/tizen_3.0.m2_tvaccepted/tizen_3.0.m2_mobileJunghyun Kim1-1/+1
- PROBLEM We use OBS to build packages in Tizen. There is a mechanism not to rebuild if the result binary is the same. For example, there is a dependency graph: A->B->C. If A is modified, B would be built. If the result RPM of B is not changed, OBS does not trigger a build of C. To effectively use this mechanism, each packages make sure that the result binary should be the same if the input source is the same. This package uses python-Cheeta package. This python-Cheeta package prints code generation time like below: [ 49s] -__CHEETAH_genTime__ = 1471828672.098387 [ 49s] -__CHEETAH_genTimestamp__ = 'Mon Aug 22 01:17:52 2016' [ 49s] +__CHEETAH_genTime__ = 1471844774.503833 [ 49s] +__CHEETAH_genTimestamp__ = 'Mon Aug 22 05:46:14 2016 This timelog is not printed if we insert settings parameter: $(CHEETAH) compile --settings='useStackFrames=False,addTimestampsToCompilerOutput=False' $< Change-Id: Ie81694a9244974b41d2cfa4d9d8bf91641648515 Signed-off-by: Junghyun Kim <jh0822.kim@samsung.com>
2016-08-29Use a sorted list of files in kickstarter to avoid unnecessary rebuilds.submit/tizen/20160831.230944accepted/tizen/common/20160901.143249Junghyun Kim1-1/+1
- PROBLEM We use OBS to build packages in Tizen. There is a mechanism not to rebuild when the result binary is the same. For example, there is a dependency graph: A->B->C. If A is modified, B would be built. If the result RPM of B is not changed, OBS does not trigger a build of C. To effectively use this mechanism, each packages make sure that the result binary should be the same if the input source is the same. There is a reason we found is that the file list given by python(os.walk(), os.listdir()), widely used executable(find), and system call(readdir()) is unordered. In this case, different OBS workers can make different results because of the file list in different order. The same thing happens in kickstarter. tools/kickstarter uses os.listdir() which returns an unordered list of files. - SOLUTION Use sorted(os.listdir()). We can obtain a sorted list of files when using sorted(). Change-Id: I9047ca08f748a938557ced46e350c24c378d439d Signed-off-by: Junghyun Kim <jh0822.kim@samsung.com>
2014-08-07Raise an error when a script is specified and not foundtizen_3.0_ivi_releasetizen_3.0.m2.a1_tv_releasetizen_3.0.m2.a1_mobile_releasetizen_3.0.m1_tv_releasetizen_3.0.m1_mobile_releasetizen_3.0.m14.3_ivi_releasetizen_3.0.2014.q3_common_releasesubmit/tizen_mobile/20141120.000000submit/tizen_ivi/20160217.000005submit/tizen_ivi/20160217.000000submit/tizen_ivi/20140825.000000submit/tizen_ivi/20140822.000000submit/tizen_ivi/20140820.000000submit/tizen_ivi/20140818.000002submit/tizen_ivi/20140818.000001submit/tizen_ivi/20140818.000000submit/tizen_common/20140812.170532submit/tizen_common/20140812.151815submit/tizen_common/20140812.150926accepted/tizen/ivi/20160218.024901accepted/tizen/common/20140812.175515tizen_3.0_ivitizen_3.0.m1_tvtizen_3.0.m1_mobiletizen_3.0.m14.3_ivitizen_3.0.2015.q2_commontizen_3.0.2015.q1_commontizen_3.0.2014.q4_commontizen_3.0.2014.q3_commonaccepted/tizen_3.0.m14.3_iviaccepted/tizen_3.0.2014.q3_commonStephane Desneux1-2/+2
This allows to break the build for image-configurations when there's an inconstency in the YAML definitions in the meta-<profile> package Change-Id: I76f0f4554ca23494b79d82cfc3498dfb23eead74 Signed-off-by: Stephane Desneux <stephane.desneux@open.eurogiciel.org>
2014-08-07Revert "fix potential error since added %suse_version"submit/tizen/20140807.133029submit/tizen/20140807.124405accepted/tizen/ivi/20140818.112928accepted/tizen/common/20140807.135400Chanho Park1-0/+5
This reverts commit e972e2e05274efdcbdf4c37beaf05873d098214e. Change-Id: I85d4874217f19fe545aa2374eafadecf8a86bebd
2014-08-06fix potential error since added %suse_versionsubmit/tizen_common/20140806.144507submit/tizen/20140806.121720accepted/tizen/common/20140806.152630Chanho Park1-5/+0
This patch fixes potential error[1] since we adds %suse_version macro[2]. [1]: https://bugs.tizen.org/jira/browse/TC-1474 [2]: https://review.tizen.org/gerrit/#/c/25292/ Change-Id: I743c16856b0d76fd544d064b8dbcf0cf825afbda Signed-off-by: Chanho Park <chanho61.park@samsung.com>
2014-07-14Enabled images filtering by specifying build targetsubmit/tizen/20140714.092215accepted/tizen/common/20140715.085520JF Ding3-16/+82
Current problem is the kickstart definitions have no target identification information in meta-* packages, which cause the generated images in product for each snapshot will be duplicated among the different targets. To resolve it, we need three modifications together: 1. Added the definition of relationship with images and targets, in meta-* packages. Sample as below: /profile/ivi/meta-ivi:/ivi-targets.yaml -> """ Targets: - Name: atom Images: - ivi-efi-i586.yaml - ivi-mbr-i586.yaml - Name: emulator Images: - ivi-mbr-i586-emul.yaml """ 2. In the building of image-configurations: add extra command line options for kickstarter command: kickstarter ... --targetdef .../%{_profile}-targets.yaml \ --target %{_repository} 3. This patch: to provide the new --targetdef and --target options. 3.1 --targetdef to specify the YAML file of targets definition 3.2 --target to specify the dedicated build target to filter images The final result will be: nothing changed to Jenkins jobs and BOSS, and the image-configuration*.rpm will not their name but will only contain the build target corresponding ks files. To keep the compatibility of all the changes, rule-1st is: The order of change integration to product server will NOT break current work as most as possible. So the integration order can be: {1, 3} -> {2}, change-2 should be the last step. Change-Id: Ie4fb251c8e6442880cb3b5386bd0dd9f4bd3adbe Signed-off-by: JF Ding <jian-feng.ding@intel.com>
2013-09-18packaging: update changelog (installerfw_plugins)tizen_3.0.m14.2_ivi_releasesubmit/tizen_ivi_panda/20140403.012014submit/tizen_ivi_genivi/20140131.025942submit/tizen/20131010.214328submit/tizen/20131004.214017ivi_oct_m2accepted/tizen/ivi/panda/20140403.014421accepted/tizen/ivi/genivi/20140131.034827accepted/tizen/20131010.214257accepted/tizen/20131010.213647accepted/tizen/20131005.063011accepted/tizen/20131004.224607accepted/tizen/20131004.224542tizen_ivi_pandatizen_ivi_genivitizen_3.0.m14.2_iviaccepted/tizen_ivi_pandaaccepted/tizen_genericaccepted/tizen/ivi/stableaccepted/tizen/ivi/geniviArtem Bityutskiy1-0/+4
Change-Id: I6989c544940ced7bbbd11031f117b27c572b0033 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-09-18kickstart.tmpl: stop using depricated "installerfw" keywordArtem Bityutskiy1-1/+1
We renamed the "installerfw" installer framework keyword to "installerfw_plugins" in MIC. MIC still supports both, but the intention is to remove the old one. Lets start using "installerfw_plugins" keyword from now on. This should fix the following MIC warning: "please, use 'installerfw_plugins' instead of 'installerfw', the latter is obsolete and will be removed in future releases" Change-Id: I21911db1a17581a8afdab934c7f7fb0a2e1852c9 Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
2013-07-08Merge commit 'refs/changes/42/5542/2' of ↵submit/tizen/20130912.090230submit/tizen/20130710.131759submit/tizen/20130708.183323accepted/tizen/20130912.195922accepted/tizen/20130912.191824accepted/tizen/20130912.145755accepted/tizen/20130710.220220accepted/tizen/20130708.234024Graydon, Tracy3-2/+14
ssh://review.tizen.org:29418/platform/upstream/kickstarter into tizen
2013-07-08Support installer framework pluginsAnas Nashif3-2/+14
Signed-off-by: Anas Nashif <anas.nashif@intel.com> Change-Id: I97eda60c201ceb00c43ad4f0817cccca0d5a4317
2013-06-29resetting manifest requested domain to floorAlexandru Cornea1-2/+2
2013-05-03Remove requirement for a default root passwordsubmit/trunk/20130503.191707submit/tizen/20130517.022855submit/tizen/20130509.180622accepted/trunk/20130506.223127accepted/tizen/20130520.095644Patrick McCarty2-0/+5
Change-Id: I6f52a49d3d7b0bca9f7c09ac8231af3fc11182c8
2013-04-10Support ks files without default usersubmit/trunk/20130410.083251submit/tizen/20130503.222855accepted/trunk/20130410.083155accepted/tizen/20130503.222652Anas Nashif2-1/+6
2012-11-15up version0.17Anas Nashif2-2/+2
2012-11-15Support custom groupsAnas Nashif2-7/+12
And use a new path for scripts and partitioning, removed the 'custom' path.
2012-11-09check for external configsAnas Nashif1-5/+5
2012-11-09support external configs via command lineAnas Nashif3-6/+21
check for external configs
2012-11-09accept multiple repo argumentsAnas Nashif4-17/+21
2012-11-09up versionAnas Nashif1-1/+1
2012-08-23added workable spec and manifest filesubmit/trunk/20120921.233347JF Ding2-16/+34
2012-08-22remove meego stuff inside specJF Ding1-3/+3
2012-07-22r -> reposAnas Nashif1-1/+1
Change-Id: I36fdc4e76f1728ba4b3145464e1a391f584c0abd Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2012-07-21mergeAnas Nashif2-11/+15
Change-Id: I07c00e71dfc2fc65fc107cfe2222d60a0edc85a7
2012-06-02support user/password in repoAnas Nashif1-3/+11
2012-06-02rename single char variableAnas Nashif1-8/+4
2012-05-31remove debugging codeAnas Nashif1-3/+0
2012-05-31resolved conflictAnas Nashif5-27/+34
2012-05-31add '%attachment' section for mic containerGui Chen2-0/+11
Signed-off-by: Gui Chen <gui.chen@intel.com>
2012-05-30update sample configs under demo/JF Ding3-25/+21
2012-05-30fixed the bug of getting path of configsJF Ding1-1/+1
2012-05-24make things work with pomoAnas Nashif1-5/+11
2012-05-16update setup.py to apply VERSION in installationJF Ding1-1/+21
2012-05-16rename README to README.md and update it as markdownJF Ding2-8/+51
2012-05-16update version for developmentJF Ding3-6/+6
2012-05-16up versionAnas Nashif1-1/+1
2012-05-15set distroAnas Nashif1-0/+3
2012-05-06fixed pathesAnas Nashif1-8/+9
2012-05-03relative external pathAnas Nashif1-2/+4
2012-04-26moved spec to packagingAnas Nashif2-0/+4
2012-04-26modularizeAnas Nashif1-11/+12
2012-04-22move everything to a moduleAnas Nashif2-58/+57
2012-04-22create own module of KSWriterAnas Nashif4-106/+112
2012-04-22create individual ks filesAnas Nashif2-9/+28
create individual ks files and add support for returning list of packages and groups to be installed
2012-04-18support empty passwd to be specifiedJF Ding1-1/+1
2012-04-18support new kickstart directive "prepackages"JF Ding2-0/+10
Using corresponding yaml keyword "PrePackages" to specify the packages which will be "pre-installed" by mic in the pre stage of image creations.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-22 19:52:49 +0000