pkg-discuss - How can I manipulate the dependency of a package

Hi,
I'm investigating
CR16520:https://defect.opensolaris.org/bz/show-bug.cgi?id520
Which complain that ddu package should denpend on
library/python-2/python-notify-26. I've checked ddu package manifest on
IPS repo server, it already have 3 dependencies there:
depend fmri=dagnostic/ddu/library@0.5.11-0.144 type=require
depend fmri=library/python-2/python-gnome-libs-26@0.5.11-0.144 type=require
depend fmri=cnsolidation/hcts/hcts-incorporation type=require
I do not know where these dependencies come from? How can I manipulate this list? like delete or add a dependency package.
Thanks,
Zhongyuan

Typically, this is handled by the distro importer. David Comay will do
that for you if you inform him of the package you owned and what it
depends on.
-Ghee
On 07/30/10 07:36 AM, zhongyuan sun - Sun Microsystems - Beijing China
>

zhongyuan sun - Sun Microsystems - Beijing China wrote:
Typically from pkgdep(1) adding dependencies for any libraries linked to
by ELF binaries, interpreters listed in the #! line of your scripts, etc.
If you deliver IPS packages to the WOS, in your package manifest.
If you deliver SVR4 packages that the WOS translates to IPS, in
the distro-import manifest for your package in the pkg gate, which
David Comay maintains.
Looks like at least as of build 140, you were delivering SVR4 packages,
and the distro-import manifest is:
http://src.opensolaris.org/source/xref/pkg/gate/src/util/distro-import/140/common/diagnostic:ddu

Please open a bug in defect.opensolaris.org under opensolaris/packaging
describing the changes you wish to see.

David and Zhong Yuan:
I had already transfer the bug 16520 to opensolaris/packaging for
further triage.
All proceeds go to American Cancer Society
http://main.acsevents.org/goto/Mary.Ding