This is a multi-part message in MIME format.
Thanks,Alexander, Luna
On 16/11/22 19:50, Alexander Reichle-Schmehl wrote:
* David Bannon <dbannon@internode.on.net> [221116 08:13]: > >> A new
update is ready, easy to switch for me, should I do QT5 this >> time ?
... > > Technical it will not cause any problems, however some of
the old > users might get confused.
.....introduce a second binary package with the > QT flavour? Maybe also rename tomboy-ng to tomboy-ng-gtk (and have >
tomboy-ng as a transistational package), for clarity?
Sorry, I need to understand a bit better. I don't intend to send Debian
another GTK2 package (?), but I already make gtk2 and qt5 versions of
tomboy-ng for distribution via github and a PPA. At present, my model is
that I have two packages -
tomboy-ng*
tomboy-ng-qt*
And both provide the tomboy-ng binary and both are listed, in control as "Provides: tomboy-ng". I like to keep the binary the same name because
I have a number of users who use the binary as part of a workflow,
typically converting between tomboy note format and markdown.
And I do not want to risk someone having both the qt5 and gtk2 version installed at the same time. Bad things would happen ...
At present, the binary checks for another binary with the same name
running as it starts up, if it finds one, it switches to the existing
instance. If there are potentially multiple binary names, that system is disabled (as it exists at present).
An existing user who has just had their tomboy-ng upgraded from, eg
0.34GTK2 will, quite possibly not notice the difference if they get
0.35Qt5, maybe might notice it looks a touch better. I routinely install qt5->gt2->qt5 and so on without problems during my testing process.
So, for me, it makes sense to call the package I will upload to mentors "tomboy-ng-qt5", the binary "tomboy-ng" and the infrastructure things
all under directories called tomboy-ng (icons, license files etc). But I
am unsure if a user with tomboy-ng (the gtk2 one) installed will get an
auto update to tomboy-ng-qt5 ??
A simpler, and maybe more reliable transition would be to just call the
qt5 package "tomboy-ng*" ?
I am not familiar what a transitional package actually does although I
see a few passing by ....
Sorry to be so detailed here, its always complicated ... Sigh...
Davo
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
Thanks,<span style="white-space: pre-wrap; display: block; width: 98vw;">Alexander, Luna</span><br>
On 16/11/22 19:50, Alexander Reichle-Schmehl wrote:<br>
<span style="white-space: pre-wrap; display: block; width: 98vw;">>
> * David Bannon <a class="moz-txt-link-rfc2396E" href="mailto:
dbannon@internode.on.net"><
dbannon@internode.on.net></a> [221116 08:13]:
>
>> A new update is ready, easy to switch for me, should I do QT5 this >> time ?
>>
>> ...
>
> Technical it will not cause any problems, however some of the old
> users might get confused.</span><br>
<span style="white-space: pre-wrap; display: block; width: 98vw;"><span style="white-space: pre-wrap; display: block; width: 98vw;">> .....introduce a second binary package with the
> QT flavour? Maybe also rename tomboy-ng to tomboy-ng-gtk (and have
> tomboy-ng as a transistational package), for clarity?</span></span><br>
Sorry, I need to understand a bit better. I don't intend to send
Debian another GTK2 package (?), but I already make gtk2 and qt5
versions of tomboy-ng for distribution via github and a PPA. At
present, my model is that I have two packages -<br>
<br>
tomboy-ng*<br>
<br>
tomboy-ng-qt*<br>
<br>
And both provide the tomboy-ng binary and both are listed, in
control as "Provides: tomboy-ng". I like to keep the binary the
same name because I have a number of users who use the binary as
part of a workflow, typically converting between tomboy note format
and markdown.<br>
<br>
And I do not want to risk someone having both the qt5 and gtk2
version installed at the same time. Bad things would happen ...<br>
<br>
At present, the binary checks for another binary with the same name
running as it starts up, if it finds one, it switches to the
existing instance. If there are potentially multiple binary names,
that system is disabled (as it exists at present).<br>
<br>
An existing user who has just had their tomboy-ng upgraded from, eg
0.34GTK2 will, quite possibly not notice the difference if they get
0.35Qt5, maybe might notice it looks a touch better. I routinely
install qt5->gt2->qt5 and so on without problems during my
testing process.<br>
<br>
<p>So, for me, it makes sense to call the package I will upload to
mentors "tomboy-ng-qt5", the binary "tomboy-ng" and the
infrastructure things all under directories called tomboy-ng
(icons, license files etc). But I am unsure if a user with
tomboy-ng (the gtk2 one) installed will get an auto update to
tomboy-ng-qt5 ??</p>
<p>A simpler, and maybe more reliable transition would be to just
call the qt5 package "tomboy-ng*" ?<br>
</p>
<p>I am not familiar what a transitional package actually does
although I see a few passing by ....</p>
<p>Sorry to be so detailed here, its always complicated ... Sigh...<br>
</p>
<p>Davo<br>
</p>
<br>
<br>
</body>
</html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)