[ SUGGESTION ] tce-load -<copy extension from path to tce/optional> option

[frimical]

I was faced with a need to load some extensions to tce/optional before beeing able to install them.

The 'download only' using the  'w' option can do it when the extension is on the web, but if it's on any other personal storage, it was not that easy to just copy the same extension and all that depends on to another location, (and specifically to tce/optional), to install it from there.

I feel that it can be very helpful if a similar option existed.

thnx

[tinypoodle]

+1

If that would be easy to implement, it could certainly increase flexibility even more.

Personally I have often found myself copying extensions from persistant storage in order to get all the benefits of having extensions mounted from tmpfs (/tmp/tce), - e.g. speed and independence of persistent storage medium after extensions are transferred - without the need of downloading them all again after each boot.

[caminati]

+1

If that would be easy to implement, it could certainly increase flexibility even more.

Personally I have often found myself copying extensions from persistant storage in order to get all the benefits of having extensions mounted from tmpfs (/tmp/tce), - e.g. speed and independence of persistent storage medium after extensions are transferred - without the need of downloading them all again after each boot.

I thought exactly these things many times. So I second this proposal.

[gutmensch]

maybe a switch like -s for --sync

tce-load -s FROMDEV TODEV [extension1] [extension2] [...]

could be useful?

tce-load -s sda1 sdb1
tce-load -s sdb1 tmp
tce-load -s tmp sda1 alsa

.. trying to create a tce/optional dir on TODEV and copying the files, if extensions are named, then only copy these one including their deps otherwise copy everything.

just my thoughts

[hiro]

put it in an other file.

tc@box:~$ wc `which tce-load`
      281       966      8152 /usr/bin/tce-load

[tinypoodle]

maybe a switch like -s for --sync

tce-load -s FROMDEV TODEV [extension1] [extension2] [...]

could be useful?

tce-load -s sda1 sdb1
tce-load -s sdb1 tmp
tce-load -s tmp sda1 alsa

.. trying to create a tce/optional dir on TODEV and copying the files, if extensions are named, then only copy these one including their deps otherwise copy everything.

just my thoughts

Sounds like a plan   

Some further thoughts:

• omitting to specify TODEV could assume .tce_dir
  
  • tce-load -si would also install - similar to -wi, but locally
    
    • reflecting the CLI implementation in appbrowser as well would be desirable

[frimical]

Personnally I thought of that just adding a new switch to tce-load script can be enough, maybe 't' or 'a' for tansfer/archive as an example, and the requested extension could be downloaded to a dummy tmp directory in the fs, or even packed to an archive/tgz file with all its deps. Then we can do whatever we want with it.

( Of course a list of extensions to transfer can be implemented either from command line or a file, ie ext.lst... deja vu? onboot.lst and friends)

Of course It would be more straight forward to copy directly to tce/optional ( Isn't this denomination outdated now? just a question between me and myself...) but this is only interesting if we want to install also from there right away.

I think the tce-load command line must stay simple. The script will guess and do the rest.

After all the tce-load script must be able to do according to these options:
# tce-load -[w a] [l c] r <path>extensionName / tcz.lst
 1-TRANSFER
   a- 'w' : transfer/download to *tce/optional*. Guess the source repository from the name of the extension ( there are only 3 cases: from path and pwd or web )
   b- 'a'   :transfer/download to *tce/archive*. Guess the source repository from the name of the extension ( there are only 3 cases: from path and pwd or web )
 2-INSTALL
    a- 'l' : loop-install or
    b- 'c': copy-install(= merge into fs)   
 3-RUN
    'r' : run it (if it is runnable of course).

of course options must be exclusive
some thoughts...

[caminati]

See http://forum.tinycorelinux.net/index.php/topic,12024.0.html.