On 10/25/07, Isaac Dupree <[EMAIL PROTECTED]> wrote:
> >> One thing we could do would be to implement extensions to
> >> the Dependencies format _first_ and worry about use-flags later.
> >>
> >> How about something adding a bracketed list of tags, like:
> >>
> >> Foo >= 1.0, < 2.0 [build-only, op
>> One thing we could do would be to implement extensions to
>> the Dependencies format _first_ and worry about use-flags later.
>>
>> How about something adding a bracketed list of tags, like:
>>
>> Foo >= 1.0, < 2.0 [build-only, optional, i686]
>> Bar >= 0.3.5 [runtime-only, !ppc]
okay, then is
On 10/25/07, Hisham Muhammad <[EMAIL PROTECTED]> wrote:
> On 10/24/07, Michael Homer <[EMAIL PROTECTED]> wrote:
> > On 10/23/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> > > I've just realized that my recent commits created (at least) one new
> > > dependency loop: GTK+ -> Cairo -> LibRSVG -> GT
On 10/24/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> 2007/10/24, Hisham Muhammad <[EMAIL PROTECTED]>:
> > On 10/22/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> > > I've just realized that my recent commits created (at least) one new
> > > dependency loop: GTK+ -> Cairo -> LibRSVG -> GTK+
> >
On 10/24/07, Michael Homer <[EMAIL PROTECTED]> wrote:
> On 10/23/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> > I've just realized that my recent commits created (at least) one new
> > dependency loop: GTK+ -> Cairo -> LibRSVG -> GTK+
> > How shold we handle these loops? By declaring LibRSVG as
2007/10/24, Hisham Muhammad <[EMAIL PROTECTED]>:
> On 10/22/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> > I've just realized that my recent commits created (at least) one new
> > dependency loop: GTK+ -> Cairo -> LibRSVG -> GTK+
> > How shold we handle these loops? By declaring LibRSVG as optio
On 10/22/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> I've just realized that my recent commits created (at least) one new
> dependency loop: GTK+ -> Cairo -> LibRSVG -> GTK+
> How shold we handle these loops? By declaring LibRSVG as optional
> dependency for Cairo we can weaken the loop, but si
On 10/23/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> I've just realized that my recent commits created (at least) one new
> dependency loop: GTK+ -> Cairo -> LibRSVG -> GTK+
> How shold we handle these loops? By declaring LibRSVG as optional
> dependency for Cairo we can weaken the loop, but si
I've just realized that my recent commits created (at least) one new
dependency loop: GTK+ -> Cairo -> LibRSVG -> GTK+
How shold we handle these loops? By declaring LibRSVG as optional
dependency for Cairo we can weaken the loop, but since we don't
support such flags yet...
The problem exists prima
