Try to package for glaxnimate
Hefee
hefee at debian.org
Sun Sep 6 07:45:55 BST 2026
Hey,
> I did some initial work for packaging glaxnimate(see repo:
> https://salsa.debian.org/ybx332/glaxnimate).
thanks for starting packaging it!
> But now I'm facing a problem. According to Debian policy, package
> needs to be linked to system library instead of their own bundled
> version.
>
> This package includes two packages, one QtColorWidgets and another
> called QtAppSetup. The first one is already in the repo.
>
> But for the second one, if we want to package it, what name should we
> use? Should we use original name or simply change the package name?
For the repo name we normally just use the upstream name, if that is not too
curious :) The important for us in Debian are the binary package name, but
there you should have a lot examples and our team website (https://qt-kde-team.pages.debian.net/) with some rules for the naming schema. In case just
ask more concrete questions about specific package names.
Just a side note: Actually if you start packaging you normally create a ITP
(intent to package) bug against wnpp package to signal the Debian community
that you are preparing something. In the case of glaxnate there exists a RFP (
request for packaging) #1071646, so you should sent an update to this bug
report, that you started packaging it.
> And just in curiosity, is pkg-kde-talk abandoned?
This list still exists and is functioning, but as we are all volunteers,
things fall down and no one replies. I would recommend you to join the irc
channel #debian-qt-kde, there you normally get faster replies.
Best regards,
hefee
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20260906/0831c3a5/attachment.sig>
More information about the pkg-kde-talk
mailing list