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

[Fab Stz]

Le lundi 19 juin 2023 18:31:46 CEST, vous avez écrit :
> On 6/18/23 6:24 PM, Fab Stz wrote:
> 
> > Le dimanche 18 juin 2023 20:33:20 CEST, vous avez écrit :
> > 
> >>     - 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.
> 
> 
> I was looking at the 3.1-stable branch rather than devel. Do you know which
> one is closer to the tagged release content?

Either master or 3.1-stable are close to the tagged contents. They seem to be 
updated only when releases are tagged, and after the release commits are 
apparently added first to the develop branch.
 
> It would definitely add some complexity, since it's difficult to know which
> commit on the branch might correspond to the tags off the branch.
 
> But I think it's likely that ftpmaster will reject the package due to the
> source-is-missing Lintian errors.

Hmm, ok, I didn't thought this would be so critical.

Anyway, I made some investigation. Findings are as follows:

- There is a bug in uscan [1] which doesn't permit us to track anything else 
than the branch that is tagged as principal by upstream. In this case, this 
branch is "develop" (and not master or 3.1-stable). Refer to [1] to see what's 
happening. Maybe I missed something.

- I managed to build the doc but that requires to resurrect `sphinxcontrib-
phpdomain` package from alioth archive. It was removed from unstable because 
no package used it. Packaging was originally created by David. I made some 
work on this and the updated package is on my salsa account [2]. If we go into 
this direction that package would need to be sponsored too.

- Another option I see is repackaging the sources by Files-Excluding 
"user_guide/" and adding manually the user_guide_src to "missing-sources".

- We could also just drop the user_guide and don't provide the doc.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992976#29
[2] https://salsa.debian.org/bastif/sphinxcontrib-phpdomain


Regards
Fab