summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/run-postinsts
AgeCommit message (Collapse)AuthorFiles
2014-01-02Update after toplevel LICENSE file checksum changeRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton1
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-09-06run-postinsts: move script execution from S98 to S99 in rcS.dLaurentiu Palcu1
Apparently, when opkg/dpkg and run-postinsts are installed in the same time, opkg/dpkg postinstall overwrites the run-postinsts link in rcS.d. This will make run-postinsts script useless and the delayed postinstalls will not be run. This issue happens only when 'package-management' is disabled and, in the same time, dpkg/opkg ends up in the image: either pulled by some dependency or manually installed. With this patch, both opkg/dpkg and run-postinsts scripts will run but the former will silently fail because the package metadata is removed from the image since 'pacakge-management' is disabled. [YOCTO #4484] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-26run-postinsts: add more logging to the log file to make things clearerChen Qi1
When all postinsts scripts succeed at system startup, it's very possible that the log file /var/log/postinstall.log is empty. This is kind of confusing, as that file is supposed to hold information about the postinsts. Add more logging to the log file to make things clearer. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-26run-postinsts: fix commentChen Qi1
The run-postinsts script also handles the #SYSCONFDIR#/rpm-postinsts directory. Add it to the comment for clarity. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18run-postinsts: Fix typoYi Zhao1
Fix a typo for stderr redirection. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-10run-postinsts: make it genericLaurentiu Palcu2
This recipe is used only when the package manager is not deployed on target and there still are delayed postinstalls that need to be run on target. At the moment, run-postinsts is targeted to dpkg/opkg. RPM uses another recipe, called rpm-postinsts which, in turn, is used even when the rpm package is deployed. This patch intends to make run-postinsts generic and deprecate rpm-postinsts. Here's why: * when opkg/dpkg are not deplyed, the meta-data files are useless. Hence, the awk script is not needed. The postinstall files are already saved in /etc/(deb|ipk)-postinsts directory and we can use the same procedure as in rpm's case; Also, the recipe is moved out from meta/recipes-devel/dpkg to meta/recipes-devel/run-postinsts. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>