Re: gambas3.desktop install idea to detect installed toolkits...

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Thursday, November 6th, 2025 at 17:59, Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 06/11/2025 à 17:00, gbWilly a écrit :
> 
> > On Wednesday, November 5th, 2025 at 18:55, Benoît Minisini
> > benoit.minisini@xxxxxxxxxxxxxxxx <mailto:benoit.minisini@gambas-
> > basic.org> wrote:
> > 
> > When it is written in the 'gambas3-gb-gui' package dependencies that:
> > 
> > Depends: gambas3-gb-gtk | gambas3-gb-gtk3 gambas3-gb-qt5 | gambas3-
> > gb-qt6
> > 
> > It should mean that 'gambas3-gb-gui' depends on at least one of these
> > packages, and 'apt' should normally ask the user which one to install.
> > 
> > I created a clean system and added OSB master as source repo.
> > I did following:
> > 
> > apt-get install gambs3-ide
> > 
> > Only gtk3 was installed since I use Mate desktop, so gambas3-gui
> > packages does exactly what it has to do, and as both you and I would
> > expect it to work.
> > 
> > install-gambas3-ide.png
> > 
> > Problem now is that when running the just installed IDE, the only
> > components available for use are those that the IDE depends on, no other.
> > 
> > run-gambas3-ide.png
> > 
> > In short, nobody does above, only install IDE. If I now would want to
> > use cairo or poppler, I would have to install them separately.
> 
> 
> And so? Why should I be prevented from running the IDE without the
> components it does not depends on? And if I want to develop a QT-only
> program on KDE without having to install all the GTK+/cairo/pango stuff
> on my system?

Well, you can by doing above, as I stated. It works and on a KDE system will ONLY install the used QT toolkit.

BTW. There is a bug in OSB recipe for Ubuntu/Debain. I had to install gambas3-gb-clipper to make the IDE start after installing gambas3-ide. Seems there is a missing dependency for gambas3-ide package. I do have it in my recipes, but on master the control file fills this in with a misc-dependencies tag that is generates by your code somewhere.



> 
> > To do a proper install of Gambas IDE you do:
> > 
> > apt-get install gambas3
> 
> 
> This is not a "proper" installation of the Gambas IDE. This is a full
> installation of all Gambas components AND the Gambas IDE.
> 

With a proper install I mean, an IDE with all components available, the default that is delivered when self compiling gambas or following all instructions on a wiki that say to install gambas3.
That will give you the FULL gambas experience and all options and freedom as a developer. As a newbee to Gambas you would not want to see a limited amount of components available in IDE because of installing only gambas3-ide. It's hard enough figuring stuff out when new to Gambas, let alone having to discover what components there might be, other that what you see in IDE.

So, yes, it is not a proper gambas3-ide install (I showed you that in above), but it is the advised method of installing gambas3. The installing only gambas3-ide is more of an expert (I've been around and know what I'm doing solution), the installing gambas3 is probably what most do, that install gambas from any repository.

So, the solution of post install script will NOT be applied when installing gambas3-ide only. It will ONLY be applied when using gambas3 packages as install. Now, when using gambas3 as install, removing a toolkit will remove gambas3 and gambas3-ide and thus gambas3.desktop.

In short, gambas3-ide install (please let me know who ever used this in real life) is NOT affected in any way or manner by the post install script.
gambas3 install IS affected by the post install script and will work as expected. So, the, I assume mostly used method of installing gambas from a repository, will have a correct representation of toolkits installed. The gambas3-ide (the expert implementation for, I presume the very few) will not. What is the problem?

gbWilly