Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: CentralWare on February 13, 2017, 01:23:53 AM
-
Is there a list (text file, DB file, etc.) somewhere within the repo which contains a file listing?
(ie: 8.x/armv7/tcz/allTCZfiles.txt or what-not)
Thanks
-
http://tinycorelinux.net/8.x/armv7/tcz/info.lst
-
http://tinycorelinux.net/8.x/x86/tcz/info.lst
Might be a glitch or possibly intentional... don't know...
-
http://tinycorelinux.net/8.x/x86/tcz/info.lst
Might be a glitch or possibly intentional... don't know...
Try
http://tinycorelinux.net/7.x/x86/tcz/ (http://tinycorelinux.net/7.x/x86/tcz/)
At present, there is no 8.x repo for x86
-
x86 isn't at version 8.x yet.
-
Goes to show what I know! :)
I was just scripting a new repo checker (to compare md5/info files) and went by what's within.
http://tinycorelinux.net/8.x/x86/tcz/
-
I think it's safe to assume when TC-8.x goes public there will be an info.lst in place, but until then anything is possible.
I usually depend on http://tinycorelinux.net/downloads.html then "Browse TCZ's" to figure out the current repo
-
@coreplayer2: The intention here is more for repository control and updating more so than use-ability for any person, so knowing whether or not a given TCZ file is within a current version, old version or one that hasn't even hit the streets isn't so much of a concern, BUT... I'm grateful none the less! 8.x/x86/tcz files which are there I'm going to "guess" and say are compiled and ready to go, so I'll look at it as a minor head-start! :) (Since the info.lst doesn't exist I had built an html tag cleaner into the app; I had thought that maybe 8.x was the latest and thus the linked directory listing was intended for manual downloading?? :) )
Cheers!
-
I'd only be guessing if there was any intent to make the soon to be 8.x repo public..
So when do we get to take this new script for a test drive ??
Sent from my iPhone using Tapatalk
-
info.lst can be relied to be there, 8.x is not released so there is no server-side support for it yet either.
-
@coreplayer2: The scripts are a work in progress... mostly due to the fact we're also rewriting start-up scripts (/etc/init.d/tc-config) and the likes to "act" differently based on what hardware it's operating on as well as other items (such as separate /tce directories for different purposes based on hardware) BUT... that's more our needs versus TCL main-stream.
1) Functionality to back-date if/when extensions are missing from the current repo version (ie: File abcd.tcz hasn't been built for 8.x Arm7 repo but exists in 7.x Arm6 or Arm7... no guarantee it would function as expected, but "should." I imagine for a stand-alone script this should be opted for instead of "always the case."
2) Functionality to version-control the repository itself (ie: separate versions.txt file similar to info.lst so that only one file need be downloaded to check versions against existing extensions) and of course, the process to generate such a file server-side.
3) A clean-up function which basically scans TCZ files which are found in tcedir and removes any extensions which are otherwise stale (AND checks the repo server-side to see which extensions are missing, especially broken dependencies, and creates a list of missing extensions.)
I'll see about getting just the tce-load replacement separated (considering it's functions are within a shared file we've been building on which is used by our custom tc-config, tce-load, tce-ab, etc.) and put together a stand-alone to put up here.
-
2 and 3 already exist? The md5sums are all in one file, so checking extension updates is fast. The apps utility, and the scripts behind it can scan for missing dependencies, or extensions not in repo, as well as other things.
-
Suggestion:
I made a script to create USB with my customizations, and it checks for updates.
It would help a lot to have a file with the content of all md5.txt files, like:
dc171ff0875b3c321e43097349983dd4 abcde.tcz
403e4566c510f3186b1e004ceb00037e abiword-dev.tcz
...
d4f2d7c2db05778476282a564281f54b zsync.tcz
Even better if this file is offered in .bzip2 format (< 42k)
-
Hi wksilva, check this out:
http://tinycorelinux.net/8.x/x86/tcz/md5.db.gz (http://tinycorelinux.net/8.x/x86/tcz/md5.db.gz)
It's currently ~56KB though.
-
Great!
This is documented somewhere? (just to know that I missed it)
Found one problem:
$ curl -s http://tinycorelinux.net/8.x/x86_64/tcz/tcl8.6.tcz.md5.txt
474b03c494c80c889da89dd926f8ba4d tcl8.6.tcz
$ md5sum tcl8.6.tcz
b1245ac4e1c4d4600e8a6a243c973b0a tcl8.6.tcz
-
I don't think it's documented, but you can find those things by reading the tce-* scripts.
Your installed tcl8.6.tcz extension needs updating?
-
Why not request each md5 file with wget for every *.tcz in your optional directory, then compare the md5sums to determine if your currently installed extension is an old version. I used this method in "tce-md5check.tcz" which fetches the most current updates in favor of the traditional database method.
besides, you only need to download the md5sums for extensions within your optional directory, not the entire repo md5sums.
You could also call tce-update, also used by APPS gui (both use the database method)
Note: the database method may not be aware of the most current updates as the database file can take a day to reflect recent updates. tce-md5check method will install the very latest updates which are often missed using the database method, this fact was discovered during testing of many other tce-md5check features.
Note: that with both tce-update and tce-md5check removing any md5.txt file from your tce store will prevent an unintentional update, thereby saving any modified extensions from loss. tce-md5check will also keep a local blacklist of extensions you might choose to blacklist from update or will download any missing md5.txt files for those you choose to allow updates.
-
One problem with removing md5.txt files though. If it's a dep of some extension that's going to be newly downloaded from the repo, tce-load will fail to do so, as it is confused about the dep being there but unable to verify its state.
Personally, I place my modified extensions in /etc/sysconfig/tcedir/optional/custom and symlink them one level up. This way tce-load won't get confused due to missing md5.txt files, I will still be notified about updates, my modifications are safe and I can easily keep track of what modified extensions I have.