Re: Preparing mass-packaging of 170 KDE application - hwo to do?

[ludo@gnu.org (Ludovic Courtès)]

iyzsong@member.fsf.org (宋文武) skribis:

> Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
>
>> Hi,
>>
>> I'm currently working on a script to mass-generate *draft* packages for
>> KDE applications. Ca. 170 of them :-) These are the ones listed at
>> <https://www.kde.org/applications/>
>>
>> The idea is to have a draft which can easily be taken and adopted.
>> Inputs will be lists at best knowledge (taken from the CMakeLists.txt
>> file). Synopsis and description are pre-filled from Debian and Mageia.
>
> Amazing works!
>
>>
>> Nevertheless 170 packages are a lot of work, which I would like to
>> distribute. Esp. checking the licenses and linting is quite some effort.
>>
>> Questions:
>>
>>   * To distribute the workload, I'd like to put the drafts somewhere.
>>     Should I push this into a wip-branch? Or hat else would be an option?
>
> Yes, please.  And instead of working on this branch directly and merge
> it as a whole, I think we can cherry-pick 1 by 1 from it.
>
>>
>>   * Should these apps be sorted alphabetically of being grouped
>>     (development, office, system, education, utilis, …)?
>
> No prefernece here.

Should the apps go in a new file, kde-applications.scm?  It would make
sure we don’t end up with a huge module.  WDYT?

Regarding synopses and descriptions, please make sure those that are
imported are generally in line with what we do (most likely they are).

Congrats on the mass import!  :-)

Ludo’.