/srv/irclogs.ubuntu.com/2023/05/22/#kubuntu-devel.txt

-queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Mantic Daily] has been updated (20230522)08:09
BluesKajHi all13:07
ahoneybun[m]Heyo BluesKaj 13:09
BluesKajhey ahoneybun[m]13:11
santa_good afternoon everybody15:19
santa_RikMills: today (or soon), if you have time and you are in the mood I would like to review/comment a few things about packaging libraries with you15:21
santa_it's relevant for the things I will be doing with kdepim from gear 21.0415:22
santa_so it would be nice if we are both on the same page15:22
santa_also (if you haven't already) I would recommend you to have a look into:15:27
santa_- https://www.debian.org/doc/manuals/maint-guide/advanced.en.html15:27
santa_- https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html15:27
santa_- debian policy 8.2: https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#shared-library-support-files15:29
santa_"If your package contains files whose names do not change with each change in the library shared object version, you must not put them in the shared library package. Otherwise, several versions of the shared library cannot be installed at the same time without filename clashes, making upgrades and transitions unnecessarily difficult."15:29
santa_↑ most of the kde libraries as they are packaged in debian, are an OUTRIGHT VIOLATION OF A DEBIAN <<MUST>> POLICY15:31
santa_(and excuse me for the caps lock, I just wanted to emphasize that part)15:31
valoriesanta_: have you discussed this issue with the kde libs devels?18:13
santa_valorie: nope, the things are in the _packaging_ side18:13
valorieI would assume that most major distros have the same issue18:13
valorieI know that naming is a BIG deal18:14
valoriefor the reason you state18:14
santa_it seems specific to the *.deb world to me, but even if they do, it's on the packaging side18:14
santa_TL;DR -> most of the kde libraries are not properly packaged in debian/ubuntu/neon18:15
valoriegot it18:15
santa_back in the days I tried to stop this, everybody dismissed the thing:18:16
santa_1. neon didn't exist by then18:16
valoriewhat does the neon team have to say about it?18:16
valorieI mean, they often package first18:16
santa_2. kubuntu people insisted it was not a problem18:16
santa_3. debian people would reject ad-hominem anything I say18:16
valorie<--- not a packager18:17
santa_valorie: that's the people of 2.18:17
valorieyes, and years more experience by now18:17
santa_and even if they fix it in neon, debian merges are going to be a problem18:17
valoriewhen I thought about learning to package just for the experience, the naming is what made me say, nope18:19
valorieit's complicated18:19
santa_it's not :P18:19
valorielol18:19
valoriewhich is why you do what you do, and I don't!18:20
valorielol18:20
* valorie must prepare for a meeting now18:20
valoriethank YOU for what you do -- analysis at a deeper level is always worthwhile18:20
santa_thank you as well :)18:23
mmikowskisanta_ I have some insight  with KDE18:36
mmikowskiis this a place where I might be able to help?18:37
mmikowskiWe are a KDE patron, so that might help18:37
santa_mmikowski: thank you very much, but no :)18:38
santa_like I said it's a packaging drama18:38
mmikowskiI didn't get all of the details, but I have spoken recently with Nate about packaging.18:39
santa_Nate is not involved in packaging afaik18:39
mmikowskinot directly, although he spoke briefly about neon packaging in our last conversation. I did too, because there are issues with QT libs and KDE frequently requiring the latest along with patches (as I expect you are very aware).18:41
mmikowskiheck, you and Rik are the folks dealing directly with those issues. But in any event, if I can help, just let me know.18:43
santa_yeah, thanks a lot18:46
mmikowskisanta_: You're welcome.18:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!