WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tce/app-browser , sparing of storage or network  (Read 352 times)

Offline mocore

  • Sr. Member
  • ****
  • Posts: 363
  • ~.~
tce/app-browser , sparing of storage or network
« on: October 21, 2022, 01:26:40 PM »

thinking about repository and related tools 

using app browser or tce to browse the extention info , request's separatly each .info/ect file viewed

and also afair separate request for each dependent tcz

i have in the past wandered ,..

0) could the time/bandwidth be reduced ?
if repo metadata (as mentioned in the below quote ) and  individual extention metadata files could be
downloaded once then used/viewed localy?.. as apposed to repeatedly requested

i guess this makes less diffrence to those with a local mirror or who know which packages are required

for the case of browseing the apps and searching/exploring posilities before testing ( if the build works at all / has required dep's ect )
waiting for many request to compleate takes time , at this point storage and bandwidth are abubdent for the most part , time is however constrained constantly

1) when downloading extentions & dependencies  could the initial conection be reused ??!!

which rased the question *exactly* what version of http is suported by tce/app-browser / tce-fetch.sh /wget and or the by the server
as this is sort of an implicit dependency of tc operation

one imho woth some consideration
and which seem a fair question(s) considering tc philosophies
 http://tinycorelinux.net/concepts.html - 'Easy, fast, and simple renew-ability and stability is a principle goal of Tiny Core.'
this appears to fall under speed consideration

i wander if anyone else has given this any thaught ( dont remenber finding any post with similar jist in the past )

all though i except ( statisticly) nothing has explicitly changed since 1.x ( apart from perhaps the server to nginx https://forum.tinycorelinux.net/index.php/topic,20499.0.html )
so it is statistically unlikely to do so in the future  :P

@mocore: I'm not certain the purpose you're after, but we already have a number of text based files found in the repo itself which may suit your purpose.
Bare in mind they're a part of the repository as opposed to the forum.

tcz/info.lst is basically a file listing of TCZs
tcz/sizelist is the above plus file lengths
tcz/tags.db is a g-zipped version of info plus tag words
tcz/provides.db is similar to an INI file with file listings for each extension
tcz/md5.db is, as you guessed it, the signatures for each file
* most of the items above are available in g-zip form, some are gz only.

Offline mocore

  • Sr. Member
  • ****
  • Posts: 363
  • ~.~
Re: tce/app-browser , sparing of storage or network
« Reply #1 on: December 08, 2022, 06:47:15 AM »

some similar/relevant observations
wrt network connections ect ... apparently inspired an alternative backed  for the core package manager
( at least that's the gist i get from scanning the thread )

http://forum.tinycorelinux.net/index.php/topic,12458.0.html - "corepkg - a new core package and updates manager"
to match all current md5 files against the ones in the repository, which generates a LOT of small web server requests to the repository and can take a long time, depending on how many extensions you have,