Summary: | qt4-r2.eclass: split into qmake-utils.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Julian Ospald <hasufell> |
Component: | Eclasses | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://git.overlays.gentoo.org/gitweb/?p=proj/qt.git;a=blob;f=eclass/qmake-utils.eclass | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Julian Ospald
2013-08-04 19:36:55 UTC
@pesa, what do you think? IIRC, you did such split in qt overlay. Is it ready to hit main tree? We are already working towards this, see qmake-utils.eclass in qt overlay (contains both eqmake4 and eqmake5). We could move it to the main tree I think, reviews are appreciated. Will we keep the eqmake code in both eclasses, or have qt4-r2 inherit qmake-utils? (In reply to Michael Palimaka (kensington) from comment #3) > Will we keep the eqmake code in both eclasses, or have qt4-r2 inherit > qmake-utils? code duplication is not good (In reply to Julian Ospald (hasufell) from comment #4) > (In reply to Michael Palimaka (kensington) from comment #3) > > Will we keep the eqmake code in both eclasses, or have qt4-r2 inherit > > qmake-utils? > > code duplication is not good I know, but it never hurts to explore all options, someone may think of an issue others did not. (In reply to Michael Palimaka (kensington) from comment #3) > Will we keep the eqmake code in both eclasses, or have qt4-r2 inherit > qmake-utils? I think about the latter. The first seems strange to me (In reply to Michael Palimaka (kensington) from comment #3) > Will we keep the eqmake code in both eclasses, or have qt4-r2 inherit > qmake-utils? I'm more inclined towards the latter, although that would mean exposing eqmake5() to qt4-r2 consumers... how is it going? I will take care of this as soon as I get back from my devaway (2nd half of October hopefully) qmake-utils.eclass is now in tree (thanks pinkbyte!) thanks |