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

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Tuesday, December 3rd, 2024 at 11:52, Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 03/12/2024 à 04:02, gbWilly a écrit :
> 
> > On Tuesday, December 3rd, 2024 at 02:03, Benoît Minisini
> > benoit.minisini@xxxxxxxxxxxxxxxx <mailto:benoit.minisini@gambas-
> > basic.org> wrote:
> > 
> > Le 03/12/2024 à 00:02, gbWilly a écrit :
> > 
> > I have been working at that, but in new master I do not know
> > where to
> > put my changes.
> > 
> > The template files for Debian are located in the 'template/debian'
> > directory. Those are the files that must be updated.
> > 
> > I get it but your debian12 recipe folder has 20 files, mine has 133!!
> > You control file has code in there to insert stuff. Impossible to compare.
> 
> > ...
> 
> 
> You don't really get it then... :-)

funny man :-)

> All files in '.obs' directory are generated by 'gambas-package-config',
> so it's useless to modify them. It's the templates inside
> 'gambas-package-config' that must be modified.

I get that the templates must be modified, but I'm not touching them as they contain @@fields@@ to do your magic and deliver missing content.
The debain.tar.gz is the only complete debian recipe (build with Benoit magic)

> Then comparison between your recipe files and the ones generated by
> 'gambas-package-config' is not done by hand! Have you never heared of
> 'diff' or 'meld'?

diff yes I know, but the difference view on git is so much more clear.
meld, no, never heard of that. I will give it a go.
 
> You must unpack the 'debian-xxx.tar.gz' file in a directory (let's name
> it 'obs-debian'), and compare it with your the directory of your own
> recipes (let's name it 'my-debian') by running the following command:
> 
> $ meld obs-debian my-debian

OK, I can work with that.
 
> You will get a automatic and graphic comparison of all files in the two
> directories line by line.
> 
> I can do that too, but if you see the differences graphically, you will
> immediately see what is wrong, far faster than me.

Yes, I understand that.
I'll get to work on it and report back.
 
> 
> > Again online on gitlab you can then very clearly see the all differences
> > between your version .dsc and the merge request .dsc even before
> > accepting and thus know where to adapt your code for making all work.
> > Those difference files in merge requests tell you more that I can even
> > explain. And those comment fields in merges can give detailed added info
> > and questions can be asked and answered, to clarify the subject.
> 
> 
> You are actually diverting 'gitlab' to make your diff. But as I said,
> you get the same result by using 'meld' locally.

Yes, gitlab gives me great insight in my own changes. Isn't that what it is for, to see what changed between original and merge?

gbWilly