[Development] Specifying module dependencies

[Hausmann Simon]

Hi,

Yeah, we used that when we tried to pin reverse dependencies, something we're not doing anymore.

Any particular reason against json, btw? Qmake can read it out of the box, as opposed to .ini. So the only other option I can think of is a very very limited qmake subset (variable.subvar = value per line and # comment).


Simon

  Original Message
From: Thiago Macieira
Sent: Wednesday, June 10, 2015 21:27
To: development at qt-project.org
Subject: Re: [Development] Specifying module dependencies


On Wednesday 10 June 2015 18:47:49 Hausmann Simon wrote:
> Hi,
>
> Why do we need to pin anything beyond the regular git submodules handling of
> qt5.git (where the information is in the tree object)?

We used to. Whether we still need to do that in the new CI, you tell me.

> In think we should have a configuration file in each module listing required
> and optional dependencies. Qt.pro can interpret that file and so can the CI
> system. To the CI system the optional dependencies are also required ones.

Fair enough, then it needs to be a simple file format. Not JSON, not PSON, etc.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development