|
|
DescriptionCondition the libsecret use on chrome desktop builds to 'use_glib'
Right now, libsecret files are added to the desktop linux
chrome builds conditioned by 'use_ozone'.
Although it works, 'use_ozone' is not the most accurate
variable to check for libsecret inclusion. A more accurate
check is 'use_glib', since GLib is the hard dependency
libsecret relies on.
Today use_ozone happens to work because it forcibly disables
use_glib.
BUG=295089
Committed: https://crrev.com/c1ce090fb362ed48b243cf3c5a926238abac36b5
Cr-Commit-Position: refs/heads/master@{#427801}
Patch Set 1 #Patch Set 2 : Condition the libsecret use on chrome desktop builds to 'use_glib' #Messages
Total messages: 30 (15 generated)
Description was changed from ========== Condition libsecret inclusion on the chrome build to 'use_glib' Right now, libsecret dependency is added to the desktop linux chrome build, conditioned by 'use_ozone'. A more accurate check should use 'use_glib', since GLib is the dependency libsecret relies on. BUG=295089 ========== to ========== Condition libsecret use on chrome desktop builds to 'use_glib' Right now, the libsecret dependency is added to the desktop linux chrome builds conditioned by 'use_ozone'. A more accurate check would use 'use_glib' instead, since GLib is the dependency libsecret relies on. BUG=295089 ==========
tonikitoo@igalia.com changed reviewers: + rjkroege@chromium.org, thestig@chromium.org
PTAL
The CQ bit was checked by tonikitoo@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Condition libsecret use on chrome desktop builds to 'use_glib' Right now, the libsecret dependency is added to the desktop linux chrome builds conditioned by 'use_ozone'. A more accurate check would use 'use_glib' instead, since GLib is the dependency libsecret relies on. BUG=295089 ========== to ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=29508 ==========
tonikitoo@igalia.com changed reviewers: + thomasanderson@chromium.org - tonikitoo@chromium.org
informal l g t m
thestig@chromium.org changed reviewers: + cfroussios@chromium.org
thestig@chromium.org changed reviewers: + cfroussios@chromium.org
The BUG= line doesn't look right.
The BUG= line doesn't look right.
Makes sense, +cfroussios to confirm. Sorry about the now triple post.
Description was changed from ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=29508 ========== to ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=295089 ==========
On 2016/10/26 16:58:29, Lei Zhang wrote: > The BUG= line doesn't look right. True, fixed.
lgtm
The CQ bit was checked by tonikitoo@igalia.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
Tree is closed. Try again in a bit?
lgtm
The CQ bit was checked by thestig@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=295089 ========== to ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=295089 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=295089 ========== to ========== Condition the libsecret use on chrome desktop builds to 'use_glib' Right now, libsecret files are added to the desktop linux chrome builds conditioned by 'use_ozone'. Although it works, 'use_ozone' is not the most accurate variable to check for libsecret inclusion. A more accurate check is 'use_glib', since GLib is the hard dependency libsecret relies on. Today use_ozone happens to work because it forcibly disables use_glib. BUG=295089 Committed: https://crrev.com/c1ce090fb362ed48b243cf3c5a926238abac36b5 Cr-Commit-Position: refs/heads/master@{#427801} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/c1ce090fb362ed48b243cf3c5a926238abac36b5 Cr-Commit-Position: refs/heads/master@{#427801}
Message was sent while issue was closed.
fwang@igalia.com changed reviewers: + fwang@igalia.com
Message was sent while issue was closed.
|