David R. Morrison wrote:
[]
The problem arises in the middle of a big compile of lots of packages.
Not only. I had two messages from fink-users as evidence, but I tried it
myself now. Turns out "fink build" and "fink install" behave
differently, the first works as intended, the second doesn't:
>From [EMAIL PROTECTED] Sat Feb 26 18:41:17 2005
From: Daniel Macks <[EMAIL PROTECTED]>
To: fink-devel@lists.sourceforge.net
Subject: Re: [Fink-devel] buildconflicts, buildlock
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disp
Daniel Macks <[EMAIL PROTECTED]> wrote:
> On Sat, Feb 26, 2005 at 03:21:30PM -0500, David R. Morrison wrote:
> > Actually, Justin, buildconflicts *had* been working recently. But as Martin
> > points out, the buildlock system has now broken it.
>
> That seems strange. In Engine.pm, the calls to
Dave Vasilevsky <[EMAIL PROTECTED]> wrote:
> On Feb 26, 2005, at 6:08 PM, David R. Morrison wrote:
> > OK, in my opinion, this behavior as reported by Robert indicates that
> > the
> > buildlock system is not yet working as it should.
>
> It's working fine, it's catching a bug in Fink right away
Daniel Macks wrote:
[]
BuildConflicts: freetype | freetype-hinting
into the info file. This never worked.
As well it shouldn't (at least not as you want), by rigorous logic of
the OR operator. Just like:
Depends: foo | bar
means something like "Depends:foo | Depends:bar", your usage means
"BC:fr
On Sat, Feb 26, 2005 at 03:21:30PM -0500, David R. Morrison wrote:
> Actually, Justin, buildconflicts *had* been working recently. But as Martin
> points out, the buildlock system has now broken it.
That seems strange. In Engine.pm, the calls to *_buildlock are tightly
wrapped around the phase_*
On Sat, Feb 26, 2005 at 12:07:57PM +0100, Martin Costabel wrote:
> I have 2 loosely related questions:
>
> 1. What is the status of the BuildConflicts mechanism? I seem to
> remember that some months ago this worked as intended, i.e. the
> buildonly packages in question were removed before build
On Feb 26, 2005, at 6:08 PM, David R. Morrison wrote:
OK, in my opinion, this behavior as reported by Robert indicates that
the
buildlock system is not yet working as it should.
It's working fine, it's catching a bug in Fink right away rather than
later. :-)
Fink is "supposed" to be able to swit
Robert T Wyatt <[EMAIL PROTECTED]> wrote:
> two cents from a beginner:
>
> At 3:55 PM -0500 2/26/05, Dave Vasilevsky wrote:
> >Buildlocks solves several problems.
> >
> >Fink's dep engine isn't always smart. [snip] 'fink install
> >bundle-gnome' [is] very likely to run into this problem.
>
> Go
no problem, I couldn't remember how it broke though I thought it was
when Max removed my Engine changes. Either way those changes I made
where wrong and I see the other side. I'll fix buildconflicts
regardless.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with th
two cents from a beginner:
At 3:55 PM -0500 2/26/05, Dave Vasilevsky wrote:
Buildlocks solves several problems.
Fink's dep engine isn't always smart. [snip] 'fink install
bundle-gnome' [is] very likely to run into this problem.
Good example! I've been installing a bunch of gnome thingies the last
On Feb 26, 2005, at 6:07 AM, Martin Costabel wrote:
2. Is there any documentation of the buildlock system, in particular
an explanation of how it works and what was the problem this is
supposed to solve? Not one of the problems I had, it seems to me. From
reading the sources, I found that there
Actually, Justin, buildconflicts *had* been working recently. But as Martin
points out, the buildlock system has now broken it.
-- Dave
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Produc
I will revive buildconflicts again, and I say again cause I wrote it
the first time and I believe Max disabled it because of an other issue
which also affected the shlibs stuff. After over a year we found away
around it for the shlibs stuff and I'm currently working on a system
for fink to add
14 matches
Mail list logo
