{"id":821,"date":"2017-12-01T12:00:22","date_gmt":"2017-12-01T12:00:22","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=821"},"modified":"2020-01-09T08:10:09","modified_gmt":"2020-01-09T08:10:09","slug":"addsource-and-addlocal","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/addsource-and-addlocal\/","title":{"rendered":"Addsource and addlocal"},"content":{"rendered":"

vinshas1 created the topic: ADDSOURCE and ADDLOCAL<\/strong>
\nExplain elaborately about ADDSOURCE and ADDLOCAL Feature configuration properties.<\/p>\n

InstallerGeek replied the topic: Re: ADDSOURCE and ADDLOCAL<\/strong>
\nADDSOURCE Property
\nThe value of the ADDSOURCE property is a list of features that are delimited by commas, and are to be installed to run from the source. The features must be present in the Feature column of the Feature Table. To install all features as run from source, use ADDSOURCE=ALL on the command line. Do not enter ADDSOURCE=ALL into the Property Table, because this generates a run-from-source package that cannot be correctly removed.
\nRemarks<\/p>\n

The feature names are case sensitive. If the LocalOnly bit flag is set in the Attributes column of the Component Table for a component of a feature in the list, that component is installed to run locally.<\/p>\n

The installer always evaluates the following properties in the following order:<\/p>\n

ADDLOCAL
\nREMOVE
\nADDSOURCE
\nADDDEFAULT
\nREINSTALL
\nADVERTISE
\nCOMPADDLOCAL
\nCOMPADDSOURCE
\nFILEADDLOCAL
\nFILEADDSOURCE
\nFILEADDDEFAULT
\nFor example:<\/p>\n

If the command line specifies: ADDLOCAL=ALL, ADDSOURCE = MyFeature, all the features are first set to run-local and then MyFeature is set to run-from-source.
\nIf the command line is: ADDSOURCE=ALL, ADDLOCAL=MyFeature, first MyFeature is set to run-local, and then when ADDSOURCE=ALL is evaluated, all features (including MyFeature) are reset to run-from-source.<\/p>\n

The installer sets the Preselected Property to a value of “1” during the resumption of a suspended installation, or when any of the above properties are specified on the command line.<\/p>\n

ADDLOCAL Property
\nThe value of the ADDLOCAL property is a list of features that are delimited by commas, and are to be installed locally. The features must be present in the Feature column of the Feature Table. To install all features locally, use ADDLOCAL=ALL on the command line. Do not enter ADDLOCAL=ALL into the Property Table, because this generates a locally installed package that cannot be correctly removed.
\nRemarks<\/p>\n

Feature names are case sensitive. If the SourceOnly bit flag is set in the Attributes column of the Component Table for a component of a feature in the list, that component is installed as run from source.<\/p>\n

The installer always evaluates the following properties in the following order:<\/p>\n

ADDLOCAL
\nREMOVE
\nADDSOURCE
\nADDDEFAULT
\nREINSTALL
\nADVERTISE
\nCOMPADDLOCAL
\nCOMPADDSOURCE
\nFILEADDLOCAL
\nFILEADDSOURCE
\nFILEADDDEFAULT
\nFor example:<\/p>\n

If the command line specifies: ADDLOCAL=ALL, ADDSOURCE = MyFeature, all the features are first set to run-local and then MyFeature is set to run-from-source.
\nIf the command line is: ADDSOURCE=ALL, ADDLOCAL=MyFeature, first MyFeature is set to run-local, and then when ADDSOURCE=ALL is evaluated, all features (including MyFeature) are reset to run-from-source.<\/p>\n

The installer sets the Preselected Property to a value of “1” during the resumption of a suspended installation, or when any of the previous properties are specified on the command line.<\/p>\n","protected":false},"excerpt":{"rendered":"

vinshas1 created the topic: ADDSOURCE and ADDLOCAL Explain elaborately about ADDSOURCE and ADDLOCAL Feature configuration properties. InstallerGeek replied the topic: Re: ADDSOURCE and ADDLOCAL ADDSOURCE Property The value of the… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[49],"tags":[191,190],"class_list":["post-821","post","type-post","status-publish","format-standard","hentry","category-general","tag-addlocal","tag-addsource"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/821","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=821"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/821\/revisions"}],"predecessor-version":[{"id":822,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/821\/revisions\/822"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=821"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=821"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=821"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}