[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Adding a README.packagers to koffice
From:       Thomas Zander <zander () kde ! org>
Date:       2005-11-15 13:11:55
Message-ID: 200511151411.56990.zander () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 13 November 2005 11:21, Cyrille Berger wrote:
> * Why it is more important now than before ?
> Well with kross in kolibs, if the packager is not aware, he will make
> kolibs have a dependency with python and ruby (and maybe more in the
> future) while kross is able to detect at runtime if python or ruby or
> both are available.
>
> So it would be best to have :
> libkoffice-kross
> libkoffice-kross-pyhon
> libkoffice-kross-ruby
[snip]

This does not make sense; if you say kross is able to detect at _runtime_ 
then the packager has no reason to split up the package.
He would simply ship the whole thing and make python a recommendation or 
suggestion instead of a dependency. [1]

I don't follow your reasoning, maybe you can tell me what I am missing?

1) see koffice-docs for example in 
http://packages.debian.org/testing/libs/koffice-data

-- 
Thomas Zander

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]