[Gambas-user] gambas slackware package creation
Benoît Minisini
g4mba5 at gmail.com
Mon Feb 4 21:54:25 CET 2019
Le 04/02/2019 à 16:03, Tim Dickson via User a écrit :
> appologies if this is double posted, I sent it first using the wrong
> email address.
> I've created a patch which adds the doinst.sh script to the package
> created by gambas, and modifies the requires file to be gambas3 which is
> what gambas is packaged as on slackware, but I haven't been able to work
> out where in the code it is creating 4 other packages which don't
> contain anything useful as far as slackware is concerned.
>
> for test project "try" I get
> -rw-r--r-- 1 root root 9221 Feb 4 15:10 try-0.0.6-noarch-1.tgz
> -rw-r--r-- 1 root root 586 Feb 4 15:10 try-gtk-0.0.6-noarch-1.tgz
> -rw-r--r-- 1 root root 588 Feb 4 15:10 try-gtk3-0.0.6-noarch-1.tgz
> -rw-r--r-- 1 root root 588 Feb 4 15:10 try-qt4-0.0.6-noarch-1.tgz
> -rw-r--r-- 1 root root 587 Feb 4 15:10 try-qt5-0.0.6-noarch-1.tgz
>
> only try-0.0.6-noarch-1.tgz contains the project with all relevant
> files. The other package files are not needed (slackware does not do
> dependency resolution, does not split packages into development and
> runtime , and every full install of slackware has qt4, thus any version
> of gambas installed has qt4 support). It should only create the one
> package file, the others are not needed, but I can't work out where they
> are being created. any pointers would be appreciated then I can submit a
> diff which allows the ide to produce expected packages.
> regards, Tim
>
You should start looking at the Package.MakePakcage() routine.
It calls "MakeTgzPackage()" to make the main package.
Then it calls "MakeSupportPackage()", that function calling
"MakeTgzSupportPackage()" to make all the GUI packages.
So, according to what you say, it should just be a matter of doing
nothing in that function.
And are you sure that there is absolutely no way to tell that a package
depends on another package with Slackware? It would be useful anyway.
--
Benoît Minisini
More information about the User
mailing list