On Thursday, 22. March 2007, Tom Albers wrote:> Hi, > > Is there some sort of way to handle the upcoming bunch of KDE4 based applications? I will release a KDE4/Qt4 based version of Mailody probably around all alpha en beta releases of KDE4, but I would not want the KDE3/Qt3 based ones removed from the repository. I guess this change happens for all applications in kde-extra''s. > > Should it be made new packages? Does it have to go through NEW again? Any thoughts?I assume that depends on the plans for the KDE 4 kde<whatever> packages. When they will be installable in parallell to kde3, then mailody do so too and needs a different pkg name. FWIW: to pkg kde4 extra application I would suggest to use <source>/branches/kde4 until CC''ed to pkg-kde-talk. Achim> > Toma > -- > http://www.mailody.net-- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- reddy@lion.austin.ibm.com
tAt Thursday 22 March 2007 15:21, you wrote:> On Thursday, 22. March 2007, Tom Albers wrote: > > Hi, > > > > Is there some sort of way to handle the upcoming bunch of KDE4 based > applications? I will release a KDE4/Qt4 based version of Mailody probably > around all alpha en beta releases of KDE4, but I would not want the KDE3/Qt3 > based ones removed from the repository. I guess this change happens for all > applications in kde-extra''s. > > > > Should it be made new packages? Does it have to go through NEW again? Any > thoughts? > > I assume that depends on the plans for the KDE 4 kde<whatever> packages.Thanks for answering. The plan for Mailody is for example: 1st April Mailody 0.5 KDE3 based. 1st May Mailody 0.??-alfa1 KDE4 based, Mailody will release at the same times KDE releases alfa, beta''s & rc''s.> When they will be installable in parallell to kde3, then mailody do so > too and needs a different pkg name.Ok, can we arrange things so it won''t end up in the NEW queue for a month? Any convention about naming? So it''s clear for the user what''s KDE4 based and KDE3 based?> FWIW: to pkg kde4 extra application I would suggest to use > > <source>/branches/kde4 until > > CC''ed to pkg-kde-talk.No responses or am I not on that list? Toma
On Wednesday 28 March 2007 09:08, Tom Albers wrote:> > I assume that depends on the plans for the KDE 4 kde<whatever> packages. > > Thanks for answering. The plan for Mailody is for example: > 1st April Mailody 0.5 KDE3 based. > 1st May Mailody 0.??-alfa1 KDE4 based, Mailody will release at the same times KDE releases alfa, beta''s & rc''s.I doubt that Debian will switch to KDE4 in one quick change, that said hopefully there will be some sort of library transition so we can have a smooth application transition. 1st April release of Mailody 0.5 we can upload quickly to unstable and then (hopefully) etch has released and thus mailody 0.5 will transition to testing within the standard 10 days. I doubt that KDE4 alpha/ beta/ rc will be released to unstable, I would imagine the team will wait until the first real release to bring KDE4 to unstable. Once KDE4 is released to unstable then mailody can also be brought to unstable and I would imagine for a while we would have the KDE3 base and applications in testing and KDE4 base and applications in unstable. Once the library transition/ applications are in a fit state I would image that KDE4 base and applications would transition to testing around the same time. Based on past experience the team may release KDE4 alpha (unlikely) / beta / rc to the Debian experimental distribution, if this happens then we can use experimental as a bit of a sandbox for integration of applications into KDE4. Then once KDE4 releases we can move to unstable. The question over releases to experimental seems to be mainly driven by available manpower and technical ability to work with the fast changing upstream releases and issues. Certainly it will easy the integration of KDE4 into Debian, but it maynot be suitable.> Ok, can we arrange things so it won''t end up in the NEW queue for a month? Any convention about naming? > So it''s clear for the user what''s KDE4 based and KDE3 based?NEW being backed up for a month is actually a rare activity. I suspect the problem at the moment is due to the ''imminent'' release of etch taking longer than expected and the release team are other wise distracted rather than processing NEW. That said if you want to enable the KDE3 & KDE4 versions of mailody to coexist on the same machine at the same time we would need to do something like have a mailody & mailody4 packages, which would have to go though new. If we just have mailody 0.5 with KDE3 dependancies and mailody 0.6 with KDE4 dependancies, then the user gets the libraries with whichever version they wish to install. And dependanices will ensure that other applications/ libs are conflict managed and removed.> No responses or am I not on that list?Looks like no response. But that is where the manpower is coming from for the KDE3/KDE4 transition. http://lists.alioth.debian.org/pipermail/pkg-kde-talk/ Mark -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20070328/46e295e5/attachment.pgp
On Wed, Mar 28, 2007 at 10:08:39AM +0200, Tom Albers wrote:> tAt Thursday 22 March 2007 15:21, you wrote: > > On Thursday, 22. March 2007, Tom Albers wrote: > > > Hi, > > > > > > Is there some sort of way to handle the upcoming bunch of KDE4 based > > applications? I will release a KDE4/Qt4 based version of Mailody probably > > around all alpha en beta releases of KDE4, but I would not want the KDE3/Qt3 > > based ones removed from the repository. I guess this change happens for all > > applications in kde-extra''s. > > > > > > Should it be made new packages? Does it have to go through NEW again? Any > > thoughts? > > > > I assume that depends on the plans for the KDE 4 kde<whatever> packages. > > Thanks for answering. The plan for Mailody is for example: > 1st April Mailody 0.5 KDE3 based. > 1st May Mailody 0.??-alfa1 KDE4 based, Mailody will release at the same times KDE releases alfa, beta''s & rc''s. > > > When they will be installable in parallell to kde3, then mailody do so > > too and needs a different pkg name. > > Ok, can we arrange things so it won''t end up in the NEW queue for a month? Any convention about naming? So it''s clear for the user what''s KDE4 based and KDE3 based? > > > FWIW: to pkg kde4 extra application I would suggest to use > > > > <source>/branches/kde4 until > > > > CC''ed to pkg-kde-talk. > > No responses or am I not on that list? >No responses yet and not plans. First let''s try to release Etch and then once kde 3.5.6/7 is unstable we can starting to play in experimental with kde 4. Ana> Toma > -- > http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk
On Thursday 29 March 2007, Ana Guerrero wrote:> No responses yet and not plans. First let''s try to release Etch and then > once kde 3.5.6/7 is unstable we can starting to play in experimental with > kde 4.full ack from here. And we also need to close or forward around 600 bugs ;) /Sune -- How to digit from the memory? You neither have to overclock a hardware, nor should ever receive the graphics board on the e-mail of the site but then you must telnet to the proxy on a analogic ethernet fan of a USB PCI icon for turning off a wordprocessor. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20070329/6cb14127/attachment.pgp
Op wo 28 mar 2007 23:48 schreef u:> On Wednesday 28 March 2007 09:08, Tom Albers wrote: > > > I assume that depends on the plans for the KDE 4 kde<whatever> packages. > > > > Thanks for answering. The plan for Mailody is for example: > > 1st April Mailody 0.5 KDE3 based. > > 1st May Mailody 0.??-alfa1 KDE4 based, Mailody will release at the same times > KDE releases alfa, beta''s & rc''s. > > I doubt that Debian will switch to KDE4 in one quick change, that said > hopefully there will be some sort of library > transition so we can have a smooth application transition. > > 1st April release of Mailody 0.5 we can upload quickly to unstable and then > (hopefully) etch has released > and thus mailody 0.5 will transition to testing within the standard 10 days. > > I doubt that KDE4 alpha/ beta/ rc will be released to unstable, I would imagine > the team will wait until the > first real release to bring KDE4 to unstable. Once KDE4 is released to > unstable then mailody can also be > brought to unstable and I would imagine for a while we would have the KDE3 base > and applications in testing > and KDE4 base and applications in unstable. Once the library transition/ > applications are in a fit state I would > image that KDE4 base and applications would transition to testing around the > same time. > > Based on past experience the team may release KDE4 alpha (unlikely) / beta / rc > to the Debian experimental distribution, > if this happens then we can use experimental as a bit of a sandbox for > integration of applications into KDE4. Then > once KDE4 releases we can move to unstable. > > The question over releases to experimental seems to be mainly driven by > available manpower and technical ability to > work with the fast changing upstream releases and issues. Certainly it will > easy the integration of KDE4 into Debian, but > it maynot be suitable. > > > Ok, can we arrange things so it won''t end up in the NEW queue for a month? > Any convention about naming? > > So it''s clear for the user what''s KDE4 based and KDE3 based? > > NEW being backed up for a month is actually a rare activity. I suspect the > problem at the moment is due to the > ''imminent'' release of etch taking longer than expected and the release team are > other wise distracted rather than > processing NEW. > > That said if you want to enable the KDE3 & KDE4 versions of mailody to coexist > on the same machine > at the same time we would need to do something like have a mailody & mailody4 > packages, which would have to go though new. > > If we just have mailody 0.5 with KDE3 dependancies and mailody 0.6 with KDE4 > dependancies, then the user gets the > libraries with whichever version they wish to install. And dependanices will > ensure that other applications/ libs are > conflict managed and removed.Hi Mark, Thanks for the responses to my mail. Things are a lot clearer now. I think it will be a difficult transition and I hope it will go ok. There are a lot of people / users excited about KDE4 and who want to install it as soon as it comes available. I want to provide a Mailody package for those users of course and that seems possible from your explanation. I think we might not need a Mailody4 package, we can just upload / experiment with it together with the upload of KDE4. As there will be no more releases of mailody for KDE3. I imagen that will go for most packages from now on. Again thanks for taking the time to explain it in detail. gr. Toma