Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: Xianwen Chen on June 20, 2010, 04:38:25 AM
-
Hi Robert,
After TCL is booted with "base norestore", only first level of TCE dependencies can be solved when loading a TCE from the other directory in appbrowser. Further dependencies are ignored.
Best regards,
Xianwen
-
Booting "base norestore" in both tc-2.11.4 and tc-3_alpha7, I get this:
$ sudo mount /dev/sda1
$ tce-load -i /mnt/sda1/tce/optional/svn.tcz
expat2.tcz: OK
libproxy.tcz: OK
openssl-0.9.8.tcz: OK
neon.tcz: OK
apr.tcz: OK
apr-util.tcz: OK
svn.tcz: OK
..am I missing something?
-
Booting "base norestore" in both tc-2.11.4 and tc-3_alpha7, I get this: $ sudo mount /dev/sda1
$ tce-load -i /mnt/sda1/tce/optional/svn.tcz
expat2.tcz: OK
libproxy.tcz: OK
openssl-0.9.8.tcz: OK
neon.tcz: OK
apr.tcz: OK
apr-util.tcz: OK
svn.tcz: OK
..am I missing something?
Yes, if you do not use tce-load but appbrowser.
-
I tried that too, i.e.
$ sudo tce-setup
$ startx
[open terminal window]
$ appbrowser
..and then select "local", "svn" and "OK" and all of the deps load.
I use microcore and I don't have an Internet connection at the moment, so there must be something with using tinycore and/or loading from the repo using appbrowser that I don't see.
-
I tried that too, i.e. $ sudo tce-setup
$ startx
[open terminal window]
$ appbrowser
..and then select "local", "svn" and "OK" and all of the deps load.
I use microcore and I don't have an Internet connection at the moment, so there must be something with using tinycore and/or loading from the repo using appbrowser that I don't see.
Well, if you don't run tce-setup.
-
This was first reported for 3.0 alpha 6 see: http://forum.tinycorelinux.net/index.php?topic=6319.30
I fixed it for alpha7 and 2.11.4. It has furthermore been reported to have been fixed by the reporting user and others. Please be sure to use 2.11.4 or 3.0 alpha 7. As you posted TCL, I am assuming that you are using Tiny Core, but you did not state which version. Use version comand to see. Otherwise I need more specifics.
-
Hi Roberts,
It is 2.11.4.
-
Loading local necessarily implies that a prior successful download via appbrowser or tce-load. Therefore other dependencies must reside in the same directory of the target. If you download via alternate means, no automatic download to try to resolve dependencies occurs. You can use appsaudit to check for missing dependencies. Also useful is to boot Tiny Core with the showapps and pause options, as perhaps a change in a dependency has occured.
-
Loading local necessarily implies that a prior successful download via appbrowser or tce-load. Therefore other dependencies must reside in the same directory of the target. If you download via alternate means, no automatic download to try to resolve dependencies occurs. You can use appsaudit to check for missing dependencies. Also useful is to boot Tiny Core with the showapps and pause options, as perhaps a change in a dependency has occured.
Hi Robert,
Thanks a lot for your reply!
Yes, all needed TCZs are inside the same directory, but not the one described in /opt. Appbrowser can load the first level of dependency when loading a package from such a path, but not further.
-
We moved away from supporting multiple tce directories awhile back; too many duplications.
Of course appbrowser is looking only at the contents of /opt/.tce_dir. It is by design.
Your options are to use tce-load or temporarily change /opt/tce_dir.
-
We moved away from supporting multiple tce directories awhile back; too many duplications.
Of course appbrowser is looking only at the contents of /opt/.tce_dir. It is by design.
Your options are to use tce-load or temporarily change /opt/tce_dir.
I see. Thanks!