Re: Building gambas on OBS

[Tim Dickson <dickson.tim@xxxxxxxxxxxxxx>]

as long as the source tar.gz or similar is available and the usual 
configure & make works, that should be fine for slackware and near 
derivatives.
my slackbuild will take either webkit2gtk4.0 or webkit2gtk4.1 although 
lists the latter as a dependency.
because deps aren't package system managed, end users can get away with 
that.
As with a number of distro's, the move from soup2 to soup3 is not 
complete because not all gnome programs have moved over, leaving people to
choice either older more complete packages or newer ones with some 
programs no longer available.

will the source remain in the usual place, or is it moving? and will it 
be able to use system libs as before or is that planned to change?
regards, Tim

On 13/11/2024 22:31, Benoît Minisini wrote:
> Le 12/11/2024 à 16:35, munix9 a écrit :
> > Am 11.11.24 um 23:12 schrieb munix9:
> > > Am 11.11.24 um 19:54 schrieb Benoît Minisini:
> >
> > Then take a look at this:
> > https://build.opensuse.org/package/show/home:munix9:gambas:test/gambas3
> > https://software.opensuse.org//download.html? 
> > project=home%3Amunix9%3Agambas%3Atest&package=gambas3
> >
> > Only one file is required: _service (the other _service:* files are 
> > created by the corresponding OBS services).
> > ...
> > This is still a proof-of-concept, there is room for optimization.
> >
> > That's it from my side for now. Next, a decision should be made as to 
> > whether OBS should be used and if so, how (organization, I have 
> > already mentioned this several times, implementation, tests, helping 
> > hands, ...).
>
> Hi,
>
> OK, let's try to use OpenSUSE Build Service.
>
> Here is what I will do now:
>
> 1) I add the same ".obs" directory than you to the root of Gambas 
> sources. I update them according to the 'master' branch.
>
> 2) I make a "gambas-package-config" Gambas project in the "app/src" 
> directory. This project will generate the contents of the ".obs" 
> directory.
>
> At the moment, I don't think that everything can be generated 
> automatically. To start, I think I can put the same component 
> description automatically everywhere. I will try to go further, but I 
> think package dependencies must be done manually, as they are 
> different between distributions.
>
> The goal is the following:
>
> 1) Every Debian/Ubuntu/ArchLinux/SuSE/Fedora packager will just have 
> to take the files from the ".obs" directory to make Gambas packages 
> for their distribution. No excuse anymore for having incorrect 
> packages of Gambas in Debian, Ubuntu (for example)...
>
> 2) All packages will be available on 'build.opensuse.org'.
>
> I just don't understand at the moment if just "x86_64" is possible, or 
> if we can have "aarch64" packages too, and if the package build must 
> be done locally or if it can occurs only on the openSUSE servers.


--
This email has been checked for viruses by AVG antivirus software.
www.avg.com