[Slackbuilds-users] I suggest to drop libksu and gksu, see what to do with qControlCenter.

[Didier Spaier]

On 11/12/2024 03:17, Jeremy Hansen wrote:
> On Tue, Dec 10, 2024, 3:16 PM Didier Spaier via SlackBuilds-users <slackbuilds-
> users at slackbuilds.org <mailto:slackbuilds-users at slackbuilds.org>> wrote:
>     I have abandoned these scripts long ago, although I be still listed as
>     maintainer by https://slackbuilds.org/advsearch.php?
>     q=Didier+Spaier&stype=maint <https://slackbuilds.org/advsearch.php?
>     q=Didier+Spaier&stype=maint>
> 
> 
> Just an FYI, I think the old maintainer generally needs to be the one to submit
> the update to mark them as unmaintained. Announcing on the mailing list just
> allows others to take over but typically won't cause the SBo admins to remove
> your name. 

Thanks for your answer Jeremy.

Let's take libksu as an example. I understand that I should:
1. Download the tarball and extract the tarball:
https://slackbuilds.org/slackbuilds/15.0/libraries/libgksu.tar.gz
2. Do in the .info:
s/MAINTAINER="Didier Spaier"/MAINTAINER="unmaintained"
s/EMAIL="didier at slint dot fr"/EMIL=""
3. make a new tarball with the changes and submit to
https://slackbuilds.org/submit/

Is this correct?

Other questions or issues:

Looking at this SlackBuild:
https://slackbuilds.org/slackbuilds/15.0/libraries/libgksu/libgksu.SlackBuild

It appears that this script is actually maintained by B. Watson so would it not
be preferable to make official that he is the current maintainer in such a case?
I think that I should first ask him if he prefers that or drop the script.

For gksu the last change is from Heinz Wiesinger on 2021-07-17 but his name does
not appear anywhere in the tarball, same for qControlCenter. What should I do?

Cheers,
Didier