Wouldn't it make sense to make a transition package "nvu" that depends on "kompozer" ? It's maybe a new project, but for what any end-user is concerned, it's the same codebase with another name. Currently when upgrading from Edgy, the nvu package is just removed and there's no hint that kompozer can/should be installed instead.
Actually, since Feisty doesn't have neither nvu proper nor kompozer, the Feisty nvu package should be empty/without dependencies. Then when upgrading to Gutsy, the Gutsy package can pull in Kompozer through a dependency.
Wouldn't it make sense to make a transition package "nvu" that depends on "kompozer" ? It's maybe a new project, but for what any end-user is concerned, it's the same codebase with another name. Currently when upgrading from Edgy, the nvu package is just removed and there's no hint that kompozer can/should be installed instead.
Actually, since Feisty doesn't have neither nvu proper nor kompozer, the Feisty nvu package should be empty/without dependencies. Then when upgrading to Gutsy, the Gutsy package can pull in Kompozer through a dependency.