since common.mk is no longer as prevalent as it once was (with platform eclass replacing the majority of users), we should rip it out of cros-workon and leave that eclass to only be uprev related.
we still have a handful of packages that use common.mk, so we can add a new eclass ("common.mk.eclass") to hold all the build logic, and update the few projects still using it to inherit that instead.
Comment 1 by bugdroid1@chromium.org
, Aug 5