Re: Initial version of 'gambas-package-config' tool

[munix9 <munix9@xxxxxxxxxxxxxx>]

Am 24.11.24 um 15:31 schrieb gbWilly:
> > Thank you, I'll take a look.
> > It would be easier to perform such steps on gitlab as merge-requests.
>
> This stuff is on gitlab in my 'Gambas3 Debian Repository'
> I guess you can just fork my develop branch (it is on gitlab) and have it all on you dekstop to play with.
>
> > This way I send my comments back via email and you send your
> > customizations - it's tedious and error-prone.
>
> Very true.
>
> This is for testing purposes now, not to clutter op Gambas gitlab.
> Once all is tested on osb and running recipe making should be centralized on Gambas3 gitlab and serve as template for the automation Benoit is building to prepare for osb builds.
>
> And that is actually the only thing that needs to be done, once Benoit has all setup, making the recipes and updating the recipes for newer versions of Gambas (an possibly as well because of a higher distro version,with dependend library names that have changed etc). Making .dsc and all and place it in a folder for osb to package with can be easily automated once you have the proper recipe
>
> gbWilly


It is implemented in 
“https://gitlab.com/munix9/gambas/-/tree/stable-test/.obs?ref_type=heads”; 
and “https://build.opensuse.org/project/monitor/home:munix9:gambas:test”; 
with changes.

The most important:

- the gambas source is not needed, it is prepared and provided by 
obs-services for the configured distributions

- we use “quilt” because “native” assumes that the debian directory is 
in the top-dir of the sources. This is not the case, the files are 
provided in the .obs directory

- obs-specific changes are required in the *.dsc files:
DEBTRANSFORM-TAR: gambas-@VERSION@xxxxxxx
DEBTRANSFORM-FILES-TAR: debian.tar.gz
or
DEBTRANSFORM-FILES-TAR: debian-Debian_11.tar.gz

- the only difference (currently) between gambas3.dsc and 
gambas3-Debian_11.dsc is the use of libwebkit2gtk-4.1-dev and 
libwebkit2gtk-4.0-dev respectively

Have a look at it and compare it with your setup.

The “Publish Flag” is currently deactivated, so that the packages and 
repositories created in obs cannot be tested (we have had this topic 
before).

Let me know if you want me to activate it.

Regards