On 11. 04. 24 11:55, Sandro wrote:
While I ponder those thoughts some more, moving forward in either
direction,
the next step would be writing a change proposal?
I'd start by:
Packaging pynose without hacks (only making it Conflict with nose, no
compatibility Provides, Obsoletes or dist-infos).
That way, pro-active packagers can switch already.
And the change proposal can then describe what will be *added* to pynose,
rather than describing the approach from scratch.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok