[pkg-php-pear] RFS: php packages looking for sponsorship

[Fab Stz]

Le dimanche 18 juin 2023 20:33:20 CEST, vous avez écrit :
> On 6/18/23 12:25 PM, Fab Stz wrote:
> 
> > Le dimanche 18 juin 2023 17:44:59 CEST, vous avez écrit :
> > 
> >>> - php-giggsey-locale
> > I think it is a tool that added these lines automatically. I can't
> > remember which one. Shall I remove them?
> 
> 
> Yes, please remove them. Perhaps it was from "gbp pq export"?

Done

> Regarding php-codeigniter-framework:
> - debian/copyright:
>    - Set Upstream-Contact (or remove template).
>    - Specify copyright for debian/tests/upstream.

Done

> - Lintian errors:
>    - Is it possible to patch the user_guide to use packaged (and 
> self-hosted) libjs-modernizr?

Done

>    - I found the sources for the user_guide at 
> https://github.com/bcit-ci/CodeIgniter/tree/3.1-stable/user_guide_src, 
> is it possible to build this during the package build? (This might 
> require to use a git commit as the upstream tree, rather than upstream's 
> tags.)

As you noted upstream puts different content on the tags that on the devel 
branch. The tags currently don't ship the tests and ship the built manual. 
That's not very nice for packaging it. I files this issue:
https://github.com/bcit-ci/CodeIgniter/issues/6172

Building the docs requires some dependencies. Some related to sphinx, and 
another dependency that is specific to that project called "CI lexer". I don't 
know if the doc could be built easily. In the meantime, I patched the manual 
to update the modernizr URL.

Wouldn't it add complexity to detect the new versions or track the updates 
directly based on the commits of the devel branch rather than using the tags?

On the other hand, by getting from the devel branch we would have the tests 
and also could use part of the newer commits before releases. Upstream tends 
to be a bit slow at releasing versions with fixes for newer versions of PHP. I 
don't know yet if they will keep the tests on the next tag.

Rgds
Fab