Max Horn [[EMAIL PROTECTED]] wrote:
> >No, it is not. I was under the impression a Conflicts:/Replaces: should
> >automatically force removal of the old package... Max, how do we make it
> >get replaced properly, then? Are we going to have to end up with a
> >Provides: system-libgl to make it r
At 8:52 Uhr -0400 09.06.2002, Benjamin Reed wrote:
>Ben Hines [[EMAIL PROTECTED]] wrote:
>> At 3:18 AM +0200 6/9/02, Max Horn wrote:
>> >Replaces works just fine, you just misunderstood what it does. If
>> >Pkg A "Replace: B", that s does *not* mean that the pkg A is a
>> >successor of pkg B.
Ben Hines [[EMAIL PROTECTED]] wrote:
> At 3:18 AM +0200 6/9/02, Max Horn wrote:
> >Replaces works just fine, you just misunderstood what it does. If
> >Pkg A "Replace: B", that s does *not* mean that the pkg A is a
> >successor of pkg B. it merely means that A and B have some files in
> >common
At 3:18 AM +0200 6/9/02, Max Horn wrote:
>Replaces works just fine, you just misunderstood what it does. If
>Pkg A "Replace: B", that s does *not* mean that the pkg A is a
>successor of pkg B. it merely means that A and B have some files in
>common. Normally you would get problems when switchin
I think perhaps that we should just remove the Conflicts line.
After all, we want people to be able to upgrade, and it actually doesn't
matter if they leave system-libgl installed after they upgrade or not.
-- Dave
From: Max Horn <[EMAIL PROTECTED]>
Subject: Re: [Fink-dev
Replaces works just fine, you just misunderstood what it does. If Pkg
A "Replace: B", that s does *not* mean that the pkg A is a successor
of pkg B. it merely means that A and B have some files in common.
Normally you would get problems when switching between packages that
share such files, bu
