Hello there, I''ve prepared a debian package for krypt [1] (KDE GUI for managing volumes encrypted with LUKS) and while looking for a sponsor, Faidon Liambotis suggested that I should contact you (pkg-kde) too. Is there any special procedure for creating a debian package for a kde program? Krypt only depends on kdelibs4 so it should be able to be used with kde4 too (right?). Is it OK to go-on and look for a sponsor? [1] http://krypt.berlios.de/ p.s. I''ve already disabled rpath. p.s.2. Please CC me
Hi, On Wed, Dec 31, 2008 at 09:54:32PM +0200, Stefanos Harhalakis wrote:> Hello there, > > I''ve prepared a debian package for krypt [1] (KDE GUI for managing volumes > encrypted with LUKS) and while looking for a sponsor, Faidon Liambotis > suggested that I should contact you (pkg-kde) too. Is there any special > procedure for creating a debian package for a kde program? Krypt only depends > on kdelibs4 so it should be able to be used with kde4 too (right?). > > Is it OK to go-on and look for a sponsor? > > [1] http://krypt.berlios.de/ >I have seen the ITP and marked to answer to the bug number, doing it now (bug Cc''ed). As you might know already, after Lenny, we are replacing KDE 3 with KDE 4, this transition will be quick but replacing all kde 3 apps for kde 4 apps, will take sime (surely too much time). So in the meantime we''ll need to keep kdelibs (and part of kdebase), but the ultimate goal is getting ride of that too (and Qt3 too!) Even if you app only needs kdelibs, it is an app that is *integrated* with kde 3.5... I really think it is best wait until it is ported to KDE 4 then package it. Ana
Thanks for the answer, On Wednesday 31 December 2008, Ana Guerrero wrote:> Hi, > > On Wed, Dec 31, 2008 at 09:54:32PM +0200, Stefanos Harhalakis wrote: > > Hello there, > > > > I''ve prepared a debian package for krypt [1] (KDE GUI for managing > > volumes encrypted with LUKS) and while looking for a sponsor, Faidon > > Liambotis suggested that I should contact you (pkg-kde) too. Is there any > > special procedure for creating a debian package for a kde program? Krypt > > only depends on kdelibs4 so it should be able to be used with kde4 too > > (right?). > > > > Is it OK to go-on and look for a sponsor? > > > > [1] http://krypt.berlios.de/ > > I have seen the ITP and marked to answer to the bug number, doing it now > (bug Cc''ed). > As you might know already, after Lenny, we are replacing KDE 3 with KDE 4, > this transition will be quick but replacing all kde 3 apps for kde 4 apps, > will take sime (surely too much time). So in the meantime we''ll need to > keep kdelibs (and part of kdebase), but the ultimate goal is getting ride > of that too (and Qt3 too!) > Even if you app only needs kdelibs, it is an app that is *integrated* with > kde 3.5... I really think it is best wait until it is ported to KDE 4 then > package it.I believe that there are some arguments for including it in debian too: a) It is not integrated. It just integrates with the desktop environment. It is a single executable binary that interracts with hal and dbus. After opening a luks device, the device is handled by KDE as a normal mapper device. It should work for gnome and KDE4 too b) From what I''ve seen, up to KDE 4.2, there is no good support for crypted volumes (correct me me if I''m wrong). This little program fills the gap. c) It''s the only way (?) to have easily accessible encrypted removable devices. d) As you said, "sime". Why not have this available for that time? e) It is a program that exists today and solves a "today''s" problem. Isn''t it better to have this available for the next year (or more), until it is ported to KDE4 or KDE4 gets support for encrypted devices? f) Are there any drawbaks for including this in debian? g) Isn''t this what happens with all other packages? AFAIK, the KDE3->KDE4 transition of programs is not a debian''s issue but the program''s developers. Why not distribute this with debian too? Anyway, without beeing a DD, as a debian user, I''d like to have this program available as a package. So, to conclude, just take a moment to reply with at least a simple go-on or don''t-go-on. I won''t argue any more. Thanks in advance and have a happy new year. p.s. Please CC me.
On Wednesday 31 December 2008 22:58:07 Stefanos Harhalakis wrote:> I believe that there are some arguments for including it in debian too:I really think that uploading any NEW packages to debian that uses kde3 libraries is a waste of everybodys time, as long as there is no plan for a kde4 edition in a near timeframe. And it is too late to be included with debian lenny, the last debian release with kde3 as desktop. - the packager for packaging - the sponsor for reviewing - ftp people for checking - qa people for asking for removal - ftp people for removing /Sune -- How could I do for installing a MIDI desktop to a application? From Word and from the preferences menu inside MacOS X you have to delete the LCD display, so that from the options within Photoshop XP you either should never load a window to the IDE command prompt to a USB modem, or must open the cable for debugging the gadget.
Hi! On Wed, Dec 31, 2008 at 11:58:07PM +0200, Stefanos Harhalakis wrote:> > I believe that there are some arguments for including it in debian too: > > a) It is not integrated. It just integrates with the desktop environment. It > is a single executable binary that interracts with hal and dbus. After > opening a luks device, the device is handled by KDE as a normal mapper > device. It should work for gnome and KDE4 too > > b) From what I''ve seen, up to KDE 4.2, there is no good support for crypted > volumes (correct me me if I''m wrong). This little program fills the gap. > > c) It''s the only way (?) to have easily accessible encrypted removable > devices. > > d) As you said, "sime". Why not have this available for that time? > > e) It is a program that exists today and solves a "today''s" problem. Isn''t it > better to have this available for the next year (or more), until it is ported > to KDE4 or KDE4 gets support for encrypted devices? > > f) Are there any drawbaks for including this in debian? > > g) Isn''t this what happens with all other packages? AFAIK, the KDE3->KDE4 > transition of programs is not a debian''s issue but the program''s developers. > Why not distribute this with debian too? > > Anyway, without beeing a DD, as a debian user, I''d like to have this program > available as a package. > > So, to conclude, just take a moment to reply with at least a simple go-on or > don''t-go-on. I won''t argue any more. >You are free to package it and ask people to sponsor it. Nobody can forbid you of uploading a proper package to Debian if you find a sponsor, but think in the work that this will carry to the distro for maybe little gain. Your package will be some time in unstable, yeah, but its final target won''t be being in a debian release given that squeeze (next release after lenny) will have KDE 4. Even if some of the work is never lost time, specially if you improve your packaging skills, introducing a new package in the archive is also work for other people in the distro like ftpmaster accepting/removing it, another developers coordinating transitions, buildd maintainers taking care of the builds across all the archs, kde team taking care of the reverse build depends, people who packages stuff in what your package relies taking care too of reverse build depends... If you have more questions ask. I hope all the above stuff helps you to understand what is the right thing to do here. ana
On Friday 02 January 2009, Ana Guerrero wrote:> > Anyway, without beeing a DD, as a debian user, I''d like to have this > > program available as a package. > > > > So, to conclude, just take a moment to reply with at least a simple go-on > > or don''t-go-on. I won''t argue any more. > > You are free to package it and ask people to sponsor it. Nobody can forbid > you of uploading a proper package to Debian if you find a sponsor, but > think in the work that this will carry to the distro for maybe little gain. > Your package will be some time in unstable, yeah, but its final target > won''t be being in a debian release given that squeeze (next release after > lenny) will have KDE 4.I believe that I cannot take such a decision myself. From my POV (as a debian user) I want this program to be in debian and that''s why i packaged it (as expected, I''m also using it). Fotis offered to sponsor it but I don''t want to introduce problems to debian, so I''ll follow your advice. As for KDE4, krypt will be usable for squeeze too and when the author ports it to KDE4 it will be ported for debian too. Having this in debian may increase the interrest of other/new users for it and they may offer to do the porting themeselves. As I see it, its main/only problem is that it will be replaced by built-in support in KDE4 sometime in the future (perhaps in KDE 4.3) but until then (1 year from now?) it is an essential tool for all encrypted-USB-stick, encrypted-USB-disk and laptop-with-encrypted-data-partition KDE3/4 users. p.s. Should I stop CCing you?
On Fri, Jan 02, 2009 at 05:11:16PM +0200, Stefanos Harhalakis wrote:> On Friday 02 January 2009, Ana Guerrero wrote: > > > Anyway, without beeing a DD, as a debian user, I''d like to have this > > > program available as a package. > > > > > > So, to conclude, just take a moment to reply with at least a simple go-on > > > or don''t-go-on. I won''t argue any more. > > > > You are free to package it and ask people to sponsor it. Nobody can forbid > > you of uploading a proper package to Debian if you find a sponsor, but > > think in the work that this will carry to the distro for maybe little gain. > > Your package will be some time in unstable, yeah, but its final target > > won''t be being in a debian release given that squeeze (next release after > > lenny) will have KDE 4. > > I believe that I cannot take such a decision myself. From my POV (as a debian > user) I want this program to be in debian and that''s why i packaged it (as > expected, I''m also using it). Fotis offered to sponsor it but I don''t want to > introduce problems to debian, so I''ll follow your advice. > > As for KDE4, krypt will be usable for squeeze too and when the author ports it > to KDE4 it will be ported for debian too. Having this in debian may increase > the interrest of other/new users for it and they may offer to do the porting > themeselves. As I see it, its main/only problem is that it will be replaced > by built-in support in KDE4 sometime in the future (perhaps in KDE 4.3) but > until then (1 year from now?) it is an essential tool for all > encrypted-USB-stick, encrypted-USB-disk and > laptop-with-encrypted-data-partition KDE3/4 users. >In case it is not clear, my advise is: if you really want to do things right, wait for the KDE 4 port, and upload it directly to Debian. If the tool is really so handy (not saying it is not, i just have not used it), it does not need to be in Debian to "encourage" its porting. Hopefully in 2 month, KDE 3.5 will be only in lenny that does not allow new packages and unstable will contain KDE 4.2.> p.s. Should I stop CCing you?I am already subscribed to pkg-kde-talk, but i do not mind it.