8 PM
> > To: Thiago Macieira; development@qt-project.org
> > Subject: Re: [Development] Specifying module dependencies
> >
> > Hi,
> >
> > Why do we need to pin anything beyond the regular git submodules
> > handling of qt5.git (where the information is
ent-bounces+louai.al-
> khanji=theqtcompany@qt-project.org] On Behalf Of Hausmann Simon
> Sent: Wednesday, June 10, 2015 9:48 PM
> To: Thiago Macieira; development@qt-project.org
> Subject: Re: [Development] Specifying module dependencies
>
> Hi,
>
> Why do we need to pi
On Mon, Jun 15, 2015 at 08:52:52AM +0200, Simon Hausmann wrote:
> We also do have at this point a duplication of repository dependencies
> in qt.pro as well as in the repository sync.profile. I do believe that
> we can eliminate this dependency without any downside, based on your
> idea of placing
On Monday, June 15, 2015 07:40:07 PM Sergio Ahumada wrote:
> On 15.06.2015 08:52, Simon Hausmann wrote:
> > Perhaps there is a misunderstanding here, so let me confirm also what
> > Joerg
> > said: At this point we're interested in discussion repository
> > dependencies. I understand that are somew
On 15.06.2015 08:52, Simon Hausmann wrote:
>
> Perhaps there is a misunderstanding here, so let me confirm also what Joerg
> said: At this point we're interested in discussion repository dependencies. I
> understand that are somewhat parallel to the qt module dependencies and I
> also
> unders
On Friday, June 12, 2015 09:47:44 AM Oswald Buddenhagen wrote:
> On Thu, Jun 11, 2015 at 08:30:37PM +, Gladhorn Frederik wrote:
> > On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
> > > you won't get rid of the redundant dependency specifications anyway,
> > > because qt.pro (and t
On Thu, Jun 11, 2015 at 08:30:37PM +, Gladhorn Frederik wrote:
> On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
> > you won't get rid of the redundant dependency specifications anyway,
> > because qt.pro (and the sync.profile's) are about repository deps,
> > while the module's re
On 11-Jun-15 18:47, Oswald Buddenhagen wrote:
> you won't get rid of the redundant dependency specifications anyway,
> because qt.pro (and the sync.profile's) are about repository deps, while
> the module's requires() (and whatever other methods they use to exclude
> themselves) are about module (
On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
> On Thu, Jun 11, 2015 at 03:43:15PM +0200, Simon Hausmann wrote:
> > On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
> > > On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> > > > Hi,
> > > >
> > > > Ok :
On Thu, Jun 11, 2015 at 03:43:15PM +0200, Simon Hausmann wrote:
> On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
> > On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> > > Hi,
> > >
> > > Ok :) let's try with reduced qmake syntax (just variables, no functions).
> >
On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
> On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> > Hi,
> >
> > Ok :) let's try with reduced qmake syntax (just variables, no functions).
> > We can still fall back to json if it's too clumsy.
> as you can "parse an
On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> Hi,
>
> Ok :) let's try with reduced qmake syntax (just variables, no functions). We
> can still fall back to json if it's too clumsy.
>
as you can "parse anything", what's wrong with parsing the function
calls from qt.pro? they m
o Macieira
Sent: Wednesday, June 10, 2015 22:21
To: development@qt-project.org
Subject: Re: [Development] Specifying module dependencies
On Wednesday 10 June 2015 19:33:37 Hausmann Simon wrote:
> Any particular reason against json, btw? Qmake can read it out of the box,
> as opposed to .ini. So
On Wednesday 10 June 2015 19:33:37 Hausmann Simon wrote:
> 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).
Didn't know th
ubvar = value per line and # comment).
Simon
Original Message
From: Thiago Macieira
Sent: Wednesday, June 10, 2015 21:27
To: development@qt-project.org
Subject: Re: [Development] Specifying module dependencies
On Wednesday 10 June 2015 18:47:49 Hausmann Simon wrote:
> Hi,
>
> Why do
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 h
system. To the CI system the optional dependencies are also required ones.
Simon
Original Message
From: Thiago Macieira
Sent: Wednesday, June 10, 2015 18:44
To: development@qt-project.org
Subject: Re: [Development] Specifying module dependencies
On Wednesday 10 June 2015 18:30:34 Frederik Gladhorn
On Wednesday 10 June 2015 18:30:34 Frederik Gladhorn wrote:
> 4) qt5.git
> in qt.pro we list all modules again, with deps:
> addModule(qtdeclarative, qtbase, qtsvg qtxmlpatterns)
> (amusingly this is not even correct, qtsvg is not a dependency of
> qtdeclarative any more)
That's an optional depen
Hi all,
when talking about how we manage dependencies in the CI system, an interesting
pain point came up during the contributors' summit:
We have several redundant overlapping, not very clear ways of specifying a
module's dependencies. Optional deps make it harder.
I'll list the 5 options I k
19 matches
Mail list logo
