Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: A Guy on June 12, 2019, 01:38:02 PM

Title: Local TCE management.
Post by: A Guy on June 12, 2019, 01:38:02 PM
So my cursory understanding is that I could download the CorePlus-current.iso and extract the .tcz files to a local web server. After doing that I could create a customized version of Tiny Core that would point to that server and be able to pull the extensions as needed from there.
Would that be correct?

Tony M.
Title: Re: Local TCE management.
Post by: Greg Erskine on June 12, 2019, 02:58:54 PM
hi Tony M.

My knowledge is limit to piCore, but it is my understanding that "/opt/tcemirror" defines what repository will be used.

If you are setting up your own repository, it requires a particular directory structure and there are auxiliary files that need to be generated.

regards
Greg
Title: Re: Local TCE management.
Post by: A Guy on June 13, 2019, 06:09:01 AM
Ah, looking at the CD there is a directory structure under the cde directory ....
Some .inslist files, perhaps they are necessary as well.

Thanks for you input, I looked at mirroring but I didn't expect it would be the exact same system.

Always a problem starting too many floors up when working with something "new to you".
Title: Re: Local TCE management.
Post by: curaga on June 13, 2019, 10:09:57 AM
No, the CD dir structure is not what the mirrors have. The mirror dirs are like

10.x/x86/tcz/ {Xvesa.tcz, Xvesa.tcz.info, ...}

The auxiliary files are used for searches, the app browser showing the .info files, etc. For direct loads, "tce-load -wi Xvesa", just the .tcz and .tcz.dep files are needed.