Hi, On Mon, Mar 03, 2008 at 11:36:46PM +1100, Harshula wrote: > Hi Ming, > > On Sun, 2008-03-02 at 11:10 -0600, Ming Hua wrote: > > > Indirect build dependency. Scim-uim build-depends on libuim-dev, which > > depends on libm17n-dev, which depends on libm17n-0, which depends on > > m17n-db. > > Thanks for the info. > > 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) Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
