On 09/06/15 14:04, Dominique Dumont wrote:
On Monday 08 June 2015 16:54:53 Tony Houghton wrote:
roxterm-common (data files, roxterm-gtk2 and roxterm-gtk3 depend on it)
roxterm-gtk2, roxterm-gtk3 (binaries)
roxterm-gtk2-dbg, roxterm-gtk3-dbg (corresponding debugging symbols)
roxterm (virtual package depending on roxterm-gtk3)
I want to replace them with a single package, "roxterm". I'm not quite
sure how to set up the package relationships to do this. I would like
the new roxterm to automatically replace roxterm-gtk3, so I think I need
to add Replaces: roxterm-gtk3 to the new roxterm, and AFAICT from the
policy manual I should use Breaks as well (rather than Conflicts).
Depending on its size, it may be better to keep roxterm-common: this package
is arch:all and this would avoid duplication these data for each arch.
IIRC I was thinking of doing that a long time ago (before the GTK2/3
split) but was advised against it because the data files weren't very
big. But they're probably considerably bigger now, mainly because of the
translations. If I did that I think I'd still have to use Breaks or
Conflicts against the GTK2 packages I'm dropping; again I'd need some
advice on exactly how to do that.
Next, you may want to consider what will happen if (or when?) gtk4 appears on
your radar screen: will you split roxterm package again ?
There were reasons for people to stick to GTK2, such as not liking GNOME
3 and because of <https://bugzilla.gnome.org/show_bug.cgi?id=649680>,
but I hope the GTK3/4 transition will be smoother and not give me
reasons to support both at once.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/557712c6.1080...@realh.co.uk
