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

[munix9 <munix9@xxxxxxxxxxxxxx>]

Am 24.11.24 um 14:29 schrieb gbWilly:
> gbWilly
>
> Gambas3 for Debian
>
> Sent with Proton Mail secure email.
>
> On Sunday, November 24th, 2024 at 01:08, gbWilly <gbWilly@xxxxxxxxxxxxxx> wrote:
>
> > On Saturday, November 23rd, 2024 at 23:19, munix9 munix9@xxxxxxxxxxxxxx wrote:
> >
> > > About the mentioned *.dsc files:
> > > For the Debian/Ubuntu build, these are the initial descriptions needed
> > > in addition to the debian archives.
> > > This is nothing specific to OBS, but OBS needs these files for operation.
> > > Again, some customization is required, but hopefully this should be
> > > painless.
> >
> >
> > That is what I kind of understood
> >
> > > https://wiki.debian.org/dsc
> > > https://www.debian.org/doc/debian-policy/ch-controlfields.html#debian-source-package-control-files-dsc
> > > https://en.opensuse.org/openSUSE:Build_Service_Debian_builds
> >
> >
> > The last link helps a lot.
> >
> > "For packages that ship `debian/` subdirectory in upstream source (known as native packages).
> >
> > The pristine tarball
> > A .dsc file"
> >
> > I suggest we build native as the originator of the Gambas3 source.
> >
> > All we need is:
> > - A pristine tarball: a source package build from git
> > - A .dsc file: is easy to make
> >
> > 1. unpack gambas source archive
> > 2. Copy recipe into root of unpacked gambas source and rename recipe folder debian (see Screen1.png)
> > 3. dpkg-source -b path/to/unpacked/source/code (see Screen2.png)
> >
> > This can be easily automated, just need to differentiate between debian11 and debian12 (mainly rules and changelog variation)
> >
> > For Ubuntu exactly the same can be done (even using debian recipe, just change rules and first line of changelog in recipe to differentiate between the different versions)
> >
> > Your testbuild on osb was based on a quilt build, so needed some extra file (Either a diff file or a Debian tarball) according to the last link.
> >
> > I always build binary only, so never had a .dsc file and no need for it for distribution.
> > But, I'm beginning to understand their needs as the .dsc file is build from recipe and contains info on packages that need to be made.
> >
> > @Benoit: I hope above steps help you in automating these needs.
> > To comply with osb build system, the recipe needs small additions and the .dsc files might need to be rebuild.
> > And you might want a recipe for latest stable and one for master I presume, that eventually becomes new stable.
>
> These 'mights' mentioned above are because of reading the instructions at https://en.opensuse.org/openSUSE:Build_Service_Debian_builds over and over again. And I read them again today.
> I think that doing the dpkg-source -b <path/to/unpacked/source/code> makes all that is needed for osb build system.
> You get:
> 1. A .dsc file
> 2. Source archive with recipe included in archive (read debian folder)
>
> @munix (Paolo): Is it possible to do another test? I have added candidate files to this mail. It is a native debian12 build for 3.19.6, suited for i386, amd64, armhf (untested) and arm64.
> If it works, my 'mights' are clear and no change to recipe is needed. If not, some minor additions to recipe should do the job.
> And if you do the build maybe a few here are willing to run some testing, see if all installs and works like expected.
>
> gbWilly

Thank you, I'll take a look.
It would be easier to perform such steps on gitlab as merge-requests.

This way I send my comments back via email and you send your 
customizations - it's tedious and error-prone.

Regards