Summary: | [Techbase] kconf_update doesn't write to update.log per default | ||
---|---|---|---|
Product: | [Websites] www.kde.org | Reporter: | David Redondo <kde> |
Component: | general | Assignee: | kde-www mailing-list <kde-www> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aacid, sitter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
David Redondo
2019-02-28 11:22:46 UTC
Pending some input on how this should actually work https://markmail.org/thread/ofaeqcabguxyohyb I am fairly confident that you simply should look for the output on stderr though. Should this be moved to kconfig? I've updated the page with both the current and future behavior as per the earlier mentioned mailing list thread. |