Differences between revisions 9 and 10
Revision 9 as of 2009-03-30 20:45:30
Size: 1638
Comment:
Revision 10 as of 2009-03-30 20:57:44
Size: 1385
Editor: ?SuneVuorela
Comment: Text crapyfied by stranger.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= KDE/Qt based package manager = = KDE4/Qt4 based package manager =
Line 3: Line 3:
 * '''Summary''': Produce a good package manager integrating nicely with Qt 4 / KDE 4 for Debian  * '''Summary''': There is no full package manager integrating nicely with Qt4/KDE4 for Debian
Line 5: Line 5:
  * Understanding of the package management system   * Understanding of package system
Line 7: Line 7:
  * Skills in KDE 4 / Qt 4 programming   * Skills in KDE4/Qt4 programming
 * '''Description''': Current possibilities is to try look at aptitude-gtk and make a -qt version (see Daniel Burrows). Another possibility is to try revive adept (see Peter Rockai)
Line 9: Line 10:
= Description =
There are 3 main paths to obtain such a package manager. One is to revive Adept. Another way is to develop and integrate KPackageKit. Finally, one could make a Qt front-end to Aptitude (see Daniel Burrows).
Note: Daniel Burrows (Aptitude developer) mentions that since aptitude-gtk is still in development, there is no way he can work on a qt version right now, at least not this summer.
Line 12: Line 12:
== Adept ==
Adept 3, a port of Adept to Qt 4, was started but then abandoned in a beta status. Adept 3 was shipped as default package manager in Kubuntu Intrepid. See Peter Rockai.
Notes: adept-3 with Qt4 was started but then abandoned in an incomplete state, but close to being ready. Adept3 was shipped as default package manager in kubuntu intrepid. From outside of Debian, we have KPackageKit but there are several issues with it coming from the fact that it tries to be an universal package manager (handling both deb and rpm). It comes from RPM-land, and thus lacks many features critical to apt/dpkg. Also, aptitude-qt won't be possible in the near future.
Line 15: Line 14:
== PackageKit ==
From outside of Debian, there is KPackageKit but there are several issues with it coming from the fact that it tries to be an universal package manager (handling both deb and rpm). It comes from RPM-land, and thus lacks many features critical to APT/dpkg.

FilipusKlutiero: Which features? Please expand or refer to further reading.

== Aptitude ==
During Summer 2008, a GTK+ front-end to Aptitude was started. The equivalent could be done with Qt. aptitude-qt won't be possible in the near future. Daniel Burrows (Aptitude's developer) mentions that since aptitude-gtk is still in development, there is no way he can work on a Qt version right now, at least not this summer.

= Executive summary =
Only apply if you know which way you want to go. Going the Adept route sounds like the current best approach. See [[SummerOfCode2009/KDE-based-packagemanager/adept-notes]] for a few more details.
Executive summary: only apply if you have a brilliant idea to solve the mess described above, but going the adept route sounds like the current best approach. See [[SummerOfCode2009/KDE-based-packagemanager/adept-notes]] for a few more details.

KDE4/Qt4 based package manager

  • Mentor: ?

  • Summary: There is no full package manager integrating nicely with Qt4/KDE4 for Debian

  • Required skills:

    • Understanding of package system
    • Skills in C++ programming
    • Skills in KDE4/Qt4 programming
  • Description: Current possibilities is to try look at aptitude-gtk and make a -qt version (see Daniel Burrows). Another possibility is to try revive adept (see Peter Rockai)

Note: Daniel Burrows (Aptitude developer) mentions that since aptitude-gtk is still in development, there is no way he can work on a qt version right now, at least not this summer.

Notes: adept-3 with Qt4 was started but then abandoned in an incomplete state, but close to being ready. Adept3 was shipped as default package manager in kubuntu intrepid. From outside of Debian, we have KPackageKit but there are several issues with it coming from the fact that it tries to be an universal package manager (handling both deb and rpm). It comes from RPM-land, and thus lacks many features critical to apt/dpkg. Also, aptitude-qt won't be possible in the near future.

Executive summary: only apply if you have a brilliant idea to solve the mess described above, but going the adept route sounds like the current best approach. See SummerOfCode2009/KDE-based-packagemanager/adept-notes for a few more details.