[Pkg-ime-devel] m17n dependencies

Harshula harshula at gmail.com
Thu Mar 6 14:46:53 UTC 2008


Hi Osamu,

On Wed, 2008-03-05 at 00:23 +0900, Osamu Aoki wrote: 
> On Mon, Mar 03, 2008 at 11:36:46PM +1100, Harshula wrote:

> > I discussed the m17n intra-dependencies with upstream a few weeks ago:
> > http://www.m17n.org/mlarchive/m17n-lib/200802/msg00011.html
> 
> Please note he is using "dependency" as the "library dependency".
> Debian dependency definitions are:
>   http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
> 
> > When I update the m17n-lib Debian source package, I'm planning on
> > libm17n to *not* depend on m17n-db. The next time I update the other
> > m17n packages, I'm planning on using upstream's suggestions.
> 
> As I understand Kenichi Handa's comment with assumption each package
> state:
> 
>  1) m17n-lib      (main)
>  2) m17n-db       (main)
>  3) m17n-contrib  (main)
>  4) m17n-docs     (DSFG non-fee)
> 
> Considering "main package must not "Depends:" or "Recommends:" on
> non-free.", I suggest:
> 
> m17n-lib package "Recommends:" m17n-db
>  ... since it is a strong, but not absolute.
> 
> m17n-lib package "Suggests:" m17n-contrib
>  ... since it is more useful with it (but not much as m17n-db)
> 
> m17n-lib package "Suggests:" m17n-doc
>  ... since it is more useful with it (provides manpage)

My current thoughts are:

libm17n-0
=========
Recommends: m17n-db, m17n-contrib (REASON: The difference between the
two is copyright ownership)
Suggests: m17n-docs

m17n-db
=======
Depends: libm17n-0 (REASON: can't use m17n-db without libm17n-0)
Suggests: m17n-docs

m17n-contrib
============
Depends: libm17n-0 (REASON: can't use m17n-contrib without libm17n-0)

m17n-docs
=========
No dependencies

cya,
#




More information about the Pkg-ime-devel mailing list