Tiny Core Linux
Off-Topic => Archive / Obsolete => Release Candidate Testing => Topic started by: roberts on January 07, 2010, 06:26:02 PM
-
The Second Release Candidate of Micro Core v2.8 (microcore_2.8rc2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/microcore/
microcore_2.8rc2.iso
microcore_2.8rc2.iso.md5.txt
Change Log for Micro Core v2.8rc2
rc1:
* Updated tce-load to allow miltiple loading, e.g., tce-load -i *.tcz
* Updated tce-load to drop ".tcz" requirement.
* Updated cd_dvd_symlinks.sh for better multiple cd and dvd devices.
* Cleanup of tce-setup & tce-update of l,m,lm, and ml code.
* Updated tce-fetch.sh to cleanup old dual repository support.
* Updated tce-update to prompt before beginning easy mode batch update operation.
* After much Team testing and input, the upx'ed kernel returns, prior kernel is in distribution files.
* Dropped symlinker by using builtin cp construct.
rc2:
* Updated tce-update for selective interaction via CLI options "query", "list", and "update".
* Dropped dropbearmulti from base.
* Updated rc.shutdown by reverse umount loops to support tcvd virtual drive.
Changes in:
Xprogs.core.tczl.md5.txt
Xprogs.core.tczl
* Updated appsaudit to allow selective removal of items "marked for deletion"
* Updated appsaudit to allow operation in tce directory as well as tce/optional directory.
* Updated appsaudit menu for smoother operation.
* Updated appsaudit new "Updates" option to "check for updates and selectively update wired into the tce-update options.
* Updated and reorganized cpanel, added "TCE Update", "USB Install", "Run Command", "Xkill", and "Xvesa Setup"
* Updated appbrowser cleanup of l,m,lm,ml code.
-
Xprogs.core.tcz did not make it into the repos, so after updateing, tce-update immediately downgrades it.
-
I can't put it in the repo until 2.8 is released, so catch-22 while in testing mode.
-
Using appsaudit from the panel and "build database", nothing appears to happen. From a terminal window, I get:
$ appsaudit
Usage: tce-audit {builddb|dependson|requiredby|nodepends|audit|auditall|delete|marked} extname
..so: $ tce-audit builddb gtkfind.tcz
/usr/bin/tce-audit: cd: line 128: can't cd to gtkfind.tcz
Building Tiny Core Extension Database from gtkfind.tcz
.............
In the logic of things, what happens next? Note that the network connection is up, but appsaudit/build database still doesn't show anything
Edit: perhaps Xprogs in the release candidates section is not the latest?
-
To build the database of dependices you need to specify a dir, e.g.:
tce-audit builddb /mnt/hda2/tce
To check for missing denpendencies on all extensions you need to specify a dir, e.g.:
tce-audit auditall /mnt/hda2/tce
To display all extensions that have no dependencies you need to specify a dir, e.g.:
tce-audit nodepends /mnt/hda2/tce
For all other reports use the full path, e.g.:
tce-audit requiredby /mnt/hda2/tce/webkit.tcz
tce-audit dependson /mnt/hda2/tce/midori.tcz
It is much easier to use appsaudit which loads up the path from user's default located in /opt/.tce_dir and makes selecting and reporting via the GUI very nice.
Of course using shell's edit capability of 'up arrorw' and 'tab completion' makes the cli easy as well.
-
Thanks - things start to work now:
$ tce-audit builddb /mnt/sda1/tce/optional
Building Tiny Core Extension Database from /mnt/sda1/tce/optional
...............
tc@box:~$ tce-audit auditall /mnt/sda1/tce/optional
For gimp1.tcz /mnt/sda1/tce/optional/glib1.tcz is missing!
For gimp1.tcz /mnt/sda1/tce/optional/gtk1.tcz is missing!
..note glib1/gtk1 are loaded from /tce at boot and gftp is also present in tce/optional and requires glib1/gtk1, but this is not mentioned.
When I open appsaudit from the panel immediately after the above and click on "Dependencies/Build Dependencies Database", I get the same message as above in the RHS pane, nothing in the LHS pane and the following choices move from greyed out to black:
1. Dependencies/Display All with No Dependencies
2. Dependencies/Display All with Missing Dependencies
3. Dependencies/Display Marked for Deletion
Clicking on 1. or 2. above opens a pop-up with the message "Error:" - should there be further text to define the error?
If I click on "Install Options/Selective Copy Install" then the extensions in /tce/optional are listed in the LHS pane and I can build copy2fs.lst by clicking on the extensions in the LHS pane - a small point, but if you click on the same extension twice, it will be listed twice.
-
Each set is independent because if you were to boot base norestore then try to load from optional gimp would not work. Until such time that a single dedicated location is used to store all dependencies we will have independent databases.
For copy2fs.lst click on RHS removes it from the list. No harm to list it twice. Easy to remove, both sides respond to click. LHS to add RHS to remove.
-
Each set is independent because if you were to boot base norestore then try to load from optional gimp would not work. Until such time that a single dedicated location is used to store all dependencies we will have independent databases.
Sure, agreed - it was more to point out that both gimp1 and gftp in tce/optional were missing glib1/gtk1, but only gimp1 was listed
-
Got it! Fixed! Thanks!
-
I probably came across the same problem. My analysis showed a wrong loop counter limit in tce-audit. Is this the same error?
Has the iso been updated?
/Lars
-
No. rc2 is still rc2.
I am not planning on any other new features.
I am in bug fix mode waiting for others to have a chance to help test and report issues before 2.8 is final.
-
Until such time that a single dedicated location is used to store all dependencies we will have independent databases.
Is this planned for 2.9?
-
Probably. It will certainly be at the beginning of a release cycle.
-
Until such time that a single dedicated location is used to store all dependencies we will have independent databases.
Is this planned for 2.9?
Change of plans. I am going to delay v2.8 and implement a whole new structure for loading and managing extensions. It will be in v2.8rc3.