Re: [gambas-package-config] Automatic generation of OBS configuration

[munix9 <munix9@xxxxxxxxxxxxxx>]

Am 30.11.24 um 20:08 schrieb Benoît Minisini:
> Hi,
>
> The 'gambas-package-config' configuration now generates in the '.obs' 
> directory:
>
> - The 'PKGBUILD' file.
> - The 'gambas3.spec' file.
> - The 'debian.tar.gz' file.
>
> I have now some requirements and questions...
>
> 1) Can Paolo, Laurent, Willy, or anyone else, check these files and 
> their corresponding template in the 'gambas-package-config' project to 
> tell me what the errors are, what is missing, and so on...

I will.
With focus on *.spec and necessary configuration for OBS for the others.

> 2) I don't generate the '*.dsc' file yet. Why these files? It seems that 
> they include information already present inside the 'debian.tar.gz' file.

If no *.dsc files exist, then no builds for Debian/Ubuntu are performed. 
*.dsc files are mandatory.

> 3) I don't generate the debian 11 specific files too yet.

No problem, then there are no builds for Debian 11.

> 4) Very important question: would it be possible, with OBS, not to just 
> make the difference between debian 11 and debian 12, but have different 
> configuration files for each distribution version? For example, one 
> '*.spec' file for each Fedora version, one 'debian.tar.gz' for each 
> Debian version, one for each Ubuntu version. And, of course, make 
> packages for all them (not -every- system version of course, but the 
> last big ones).

Theoretically yes, it's just a question of effort.

For each repository that is configured in the project, a separate build 
description can be created - for Debian/Ubuntu then additionally the 
*.tar.gz - with Arch, however, this makes little sense, I think.
E.g.:
gambas3-15.6.spec
gambas3-16.0.spec
gambas3-openSUSE_Tumbleweed.spec
gambas3-Fedora_40.spec
gambas3-Fedora_41.spec
gambas3-Debian_12.dsc + debian-Debian_12.tar.gz
gambas3-xUbuntu_22.04.dsc + debian-xUbuntu_22.04.tar.gz
...

With openSUSE/Fedora or *.spec in general, it doesn't really make much 
sense either, as the *.spec format is very flexible in terms of 
configuration - but yes, you should be able to do it and, above all, 
test it.

> Thanks again for all your help, guys!