Why does open-vm-tools-x not load all extensions it depends on?

[Ulysses_]

Alright, thanks, I'll do the recommended check later.  You are confirming ondemand works as expected, but I am seeking whether the install puts all dependencies on the left or the right of the OnBoot table.

[danielibarnes]

I am seeking whether the install puts all dependencies on the left or the right of the OnBoot table.

If you download an extension as "OnDemand" it will be on the left. If you download an extension as "OnBoot" it will appear on the right. This will never change unless you do so explicitly.

[Ulysses_]

Gone through the instructions with fresh downloads instead of loads to eliminate anything local. And started with a fresh install of current release TC 3.5.1. This is not the one you're working on, and where maybe you've got just one table for both onboot and ondemand whereas in 3.5.1 there are two separate tables.  

Attachment 1 is the table of OnDemand, which is as expected: all on the left, except Xlibs on the right.  

Attachment 2 is the table of OnBoot. All dependencies of open-vm-tools-x are on the left!  Whereas open-vm-tools-x, is alone on the right!  They should all be on the right!

As it is now, arbitrary screen resize does not work, some glitch maybe.  Right-clicked on the desktop menu under ondemand and Xlibs and it still does not work.  After a reboot with backup, it now works.  Maybe other features do not work if Xlibs is missing?

Typing "free" now reports 383200 kB free in the second line, whereas if we now go to OnBoot and click on all the extensions so they go to the right together with open-vm-tools-x, and reboot with backup, "free" reports 381400 kB free in the second line.  

That is a difference of 1800 kB.  It says to me the dependencies are not loaded the first time, or they are not functional.  But they should be, because then you know how much memory you've got left for the browser etc and therefore how many VMs you can run in a given host. This is important if you want to sandbox several internet-facing applications so any infection is contained but you can still run as many of them as possible simultaneously.

[gerald_clark]

Do you not read any of the replies to your posts.
Dependencies do not get set to anything.
They are automatically loaded WHEN the program that needs them is loaded.
They do NOT get added to onboot.
They do NOT get added to ondemand.

[Ulysses_]

How do you explain the memory difference then?    I bet you didn't read that far.

[tinypoodle]

To make it even more clear: dependency resolving works all the same on systems with PPR where onboot and ondemand are not used at all.

P.S.: Attachment of type "tif" are not of high compatibility, "png" is preferable  

[gerald_clark]

Installing extensions does not consume significant memory if the extensions are loop mounted.
libraries and binaries are not loaded into RAM until they are executed.

[Ulysses_]

To make it even more clear: dependency resolving works all the same on systems with PPR where onboot and ondemand are not used at all.

It might be useful to NOT show required extensions in onboot or ondemand tables because this is misleading.  People might click on required extension names and think something useful is happening when extensions change side from left to right on either of the two tables.

Installing extensions does not consume significant memory if the extensions are loop mounted.

Open-vm-tools-x is supposed to run at all times, loop mounted or otherwise. It requires an executable in memory at all times. It is not like firefox that only uses memory when you manually launch it.

libraries and binaries are not loaded into RAM until they are executed.

So what do you think was done differently the second time that made open-vm-tools-x load more libraries into RAM? 

Note: I didn't use copy-paste, and time sync by default is off.  Didn't resize the screen just before noting the "free" readings, the resize was a test that open-vm-tools-x is working in separate sessions.  You can do the same and do exactly the same in both cases.

P.S.: Attachment of type "tif" are not of high compatibility, "png" is preferable   

That's easy then, png from now. Was the tif viewable at least?

[gerald_clark]

The left panel in AppsAudit is just the downloaded extensions that are not currently in onboot or ondemand.
It is not AppsAudit's job to filter out extensions that you may not want to select.
It is simply a GUI extension to command line tools that is intended to make it easier for YOU to make selections.

[danielibarnes]

The left panel in AppsAudit is just the downloaded extensions that are not currently in onboot or ondemand.
It is not AppsAudit's job to filter out extensions that you may not want to select.
It is simply a GUI extension to command line tools that is intended to make it easier for YOU to make selections.

AppsAudit does not filter out the dependencies of extensions already in either OnDemand or OnBoot. Whether or not it should is a user interface issue because it does not affect the operation. Dependencies of OnBoot extensions will still be loaded "OnBoot" and dependencies of "OnDemand" extensions which are not already loaded will be loaded "OnDemand."

[Ulysses_]

The left panel in AppsAudit is just the downloaded extensions that are not currently in onboot or ondemand.

That's not the left that we're looking on here.  We are looking on the left of the OnBoot table and the left of the OnDemand table (3.5.1) or the two sides of the joint table in (c.r.candidate).  Required extensions are misleading there.  Only top extensions are logically expected there, if required extensions are loaded automatically.

Otherwise you click on required extensions in those/that tables/table and your clicks and movements left to right have no effect.

[gerald_clark]

We are talking of the same left panel.
The left panel of both onboot and ondemand is all downloaded extensions not explicitely included in onboot or ondemand.
Dependencies are not considered here.  You may include some or all dependencies as you see fit, but you must do it manually.

[Ulysses_]

We are talking of the same left panel.
The left panel of both onboot and ondemand is all downloaded extensions not explicitely included in onboot or ondemand.
Dependencies are not considered here.  You may include some or all dependencies as you see fit, but you must do it manually.

Is that 3.5.1 or the c.r.candidate you're looking at (never seen the c.r.cand.)?

Either way, it is not logical that you can click on dependencies and move them to the right.  Doesn't anyone see the misleadingness of this?

[Ulysses_]

Hell this thread wouldn't ever had existed if those darned dependencies were hidden from onboot and ondemand tables in 3.5.1.  They have no place in these tables.

[tinypoodle]

You seem to overlook that one and the same extension could as well serve
A: as a standalone app (e.g. it could make sense to have TC base and gpm being the only extension just to have a console mouse)
B: as an optional dep to some apps (e.g. gpm with irssi)
C: as a hard dep to some other apps (e.g. gpm and links)

As for the tif attachments, opera would prompt which app to open them with.