Re: Gambas 3.19.6 and 3.19.90 recipes

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Sunday, November 17th, 2024 at 17:54, T Lee Davidson <t.lee.davidson@xxxxxxxxx> wrote:

> On 11/15/24 12:24, Benoît Minisini wrote:
>
> > What's the difference between the "-quilt" and the "-native" folders?
>
>
> I would also like a clear answer to this question as, even with all my previous research, I still don't fully understand the
> difference between the 'quilt' and 'native' formats.

Well, I did research it several times and didn't really get an good answer, nowhere.
But I did experiment with the two concepts and made a quite some package over time, sometimes whit a gap of many, many moons.

I noticed that version numbers work different, as I mentioned in an earlier post.

I can explain how I use it differently:

Standard I build quilt using numbers like:
3.19.5-1 (native does not allow that, just 3.19.5)
If later turns out something was not quite right I can do a 3.19.5-2 build and so on...

You might recognize this  added -1 or -2 etc. for same version, from the Gambas packager in the IDE if you ever use it to make a debian package for your application.

But for example on an intranet server at work I host gambas 3.18.4 with some backports from development. That is a native build.
I used the quilt recipe 3.18.4-1 and renamed quilt to native, in the file format and changed the version format in the first line of the changelog (very important line).
That is all the difference (and of course I used a modified 3.18.4 source code).

The recipes found on my gitlab in recipes folder are all native, in recipes-dev I use a quilt for current version to test and package for the downloadable repository archives.

The objections in your linked discussion about not being able to build with quilt is a matter of adding an argument to the build tool and it works.

So, I think the quit versus native has to do mainly with the debian ecosystem for official packaging.

Let's have a look at for example Gambas on Debian official:

Upstream is considered Gambas at gitlab (https://gitlab.com/gambas/gambas)
Debian have their own gitlab and a team for Gambas packaging (https://salsa.debian.org/gambas-team/gambas3)

Gambas team at salsa.debian.org makes recipes, with patches to remove things the debian ecosystem (lintian) considers problems/errors.
So, they make recipes and patch files (difference files actually) to remove errors in lintian reports.
See their recipe folder: https://salsa.debian.org/gambas-team/gambas3/-/tree/master/debian
Check folder patches to understand what I mean with patches.

The Debian building system uses a tool named gbp (git-buildpackage). This can build with the source on gitlab (upstream) and recipe on salsa.
It is available on debian (see screenshot)

When a Debian package team made a new recipe they can initiate a build request and next, I guess a bunch of vm's in a bunch of different architectures, start building the packages.
During the making of these packages all kinds of checks and balances are done and reported back with build reports, lintian checks and so on. See: https://tracker.debian.org/pkg/gambas3

These reports then determine if packages are accepted to sid or if the package team has to go back to the drawing board and create new recipe/patch or whatever is needed.
The above mentioned recipes made by Debian team are quilt and so are most of the recipes made on salsa.
To know, see their recipe folder: https://salsa.debian.org/gambas-team/gambas3/-/tree/master/debian
Check file source/format -> quilt

I do believe that tools and stuff debian developed themselves are packaged native.
Have a look at recipe for debhelper (a debian original so to speak: https://salsa.debian.org/debian/debhelper/-/tree/main/debian)
Check file source/format -> native

This is my understanding of the matter so far.

Thanks for the links

gbWilly

Attachment: git-buildpackage.png
Description: PNG image