Tiny Core Linux

Tiny Core Base => TCB Talk => Topic started by: jls on January 06, 2011, 08:40:28 AM

Title: ondemand behaviour in case the extension in not in the optional dir
Post by: jls on January 06, 2011, 08:40:28 AM

should the scripts generated by ondemand download from the net the extension if missing locally?

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: gerald_clark on January 06, 2011, 08:51:03 AM

How does it get in ondemand if it is not in optional?

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: jls on January 06, 2011, 08:52:40 AM

u ondemanded the extension in the past but then u deleted the tcz

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: Guy on January 06, 2011, 02:40:44 PM

No

You should not delete the tcz if you want to use it.

You can't expect tiny core to do things you don't ask it to do. Other people may not want it to do that.

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: gerald_clark on January 06, 2011, 02:51:20 PM

It is very easy to put a script in ~/.local/bin that checks to see if the binary exists, and tce-load -iw the extension if it does not.
I do this for dropbear and midnight-commander, as they have no icon for ondemand.

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: tinypoodle on January 06, 2011, 03:14:05 PM

I could imagine that this idea could be implemented as "ondemand from cloud".

If it could be implemented in a way to rely only on files in backup so an existing PPR would not be a requisite, then it could possibly enhance the (already impressive) nomadic capacities of TC even further.

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: gerald_clark on January 06, 2011, 04:36:03 PM

Ahh, if there is no ppr, where are you going to store this ondemand-from-cloud?

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: tinypoodle on January 06, 2011, 06:11:45 PM

What I had in mind would be a persistent personal ondemand configuration, which might allow to use ondemand in a similar way as using extensions when in cloud mode with backup.

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: jur on January 06, 2011, 07:17:23 PM

Quote from: tinypoodle on January 06, 2011, 06:11:45 PM

What I had in mind would be a persistent personal ondemand configuration, which might allow to use ondemand in a similar way as using extensions when in cloud mode with backup.

I have my setup like this. I can delete everything in tce/optional (except onboot stuff), and recover fully.

Now if tce-load also fetched stuff from the repo if missing locally, it would be a fully recoverable system. Has my vote.

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: Guy on January 06, 2011, 11:37:18 PM

The user needs to be given a choice.

The minimum requirement would be to notify the user that the extension is missing, and ask if the user wants to download it.

But then, why not just suggest the user download it using the app browser?

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: jur on January 06, 2011, 11:50:42 PM

Choice is good - could be a radio button in appbrowser, to select an option to automatically download missing extensions.

Title: Re: ondemand behaviour in case the extension in not in the optional dir
Post by: gerald_clark on January 07, 2011, 07:49:08 AM

Automatically "attempting" to download missing dependencies during application load will
result in confusion to many users when applications fail to load.
Forcing the download of dependencies when downloading an application with AppBrowser
gives the user feedback on the success or failure of the installation.

Just how do you decide what commands need to be downloaded on-demand, and how do you know the extension names?