Having some arguments with someone about dependencies of libraries,
I've posted here to have this sorted out.
Assume you have:
libfoo libc5 compatibility library
libfoo-altdevlibc5 compatibility development package
libfoog libc6 library
libf
On Wed 26 Nov 1997, Bdale Garbee wrote:
> In article <[EMAIL PROTECTED]> you wrote:
>
> : their packages are available, ours not...
>
> I think there are two things that I must have missed in the discussion on this
> topic:
>
> - why are there two sets of KDE packages? One should be suffi
> (For simplity and without loss of generality, I'm just describing the
> solution for kdebase and kdegraphics. Furthermore, the "Depends:" lines
> have been simplified.)
>
> The Debian packages:
> Package: kdelibs0g
>
> Package: kdebase
> Depends: kdelibs0g, ...
>
> Package: kdegraphics
>
> Won't our turning off --force-overwrite in 2.0 be a more realistic
> solution of this problem? Aren't most package conflicts really
> related to their usage of competing file structures? Or am I totally
> off-base here?
kde's version of kdelib is not compatible with my kdelib :
we have differe
Andreas,
please tell us which problems you see with the following solution.
(For simplity and without loss of generality, I'm just describing the
solution for kdebase and kdegraphics. Furthermore, the "Depends:" lines
have been simplified.)
The Debian packages:
Package: kdelibs0g
Package:
On Wed, Nov 26, 1997 at 10:07:08PM -0700, Bdale Garbee wrote:
> In article <[EMAIL PROTECTED]> you wrote:
>
> : their packages are available, ours not...
>
> I think there are two things that I must have missed in the discussion on this
> topic:
>
> - why are there two sets of KDE packages
In article <[EMAIL PROTECTED]> you wrote:
: their packages are available, ours not...
I think there are two things that I must have missed in the discussion on this
topic:
- why are there two sets of KDE packages? One should be sufficient.
- why can't "your" KDE packages be mad
7 matches
Mail list logo
