2.4 Roadmap

[roberts]

It has been decided by Team Tiny Core to move to a single extension type, the tcz.
This will be implemented starting with v2.4. More announcements to follow both here, regarding the base, and in the 2.x Extension area.

[bmarkus]

Sounds good. Is there a timeframe already?

[tclfan]

Will naming convention change from tcz to tce?

[roberts]

Name will not change. Still will be tcz. Already many new extensions have been posted only as tcz, therefore those accessing only tce repository are already not seeing new extensions.

With each release of TC/MC many new features and very importantly, bugs are fixed. It is in the best interest for each to upgrade and stay current.

The webpage of the tce repository will not be removed but should be treated as archived. This will happen when 2.4 is released. Web only access to this page will be similar to the v1.x pages.

Support for tces will be removed in 2.4 Appbrowser when run from prior 2.x will display an error message when trying to access the tce repository.

It is important to note, that you are not losing functionality. Each tcz can be loaded into ram, just as the tce did.

[roberts]

Sounds good. Is there a timeframe already?

I may issue a v2.3.2 just because I like to get bug fixes out ASAP and many won't touch a release candidate. I expect nearly weekly cuts to coninue as has been the case. I expect 2.4 to have a longer release candidate cycle.

There will be many changes that need to be coordinated, code, webpages and documentation.
Another reason that a likely additional minor release is likely.

[sci_fi]

Good morning.

A couple of TC newbie questions regarding this:

1. I have been using .tce files exclusively up till now. Should I redo my /tce folder to contain only the .tcz versions to insure future compatibility?

2. Will mix and match of tce and tcz files in my /tce folder continue to work or does .tce simply stop working  with 2.4?

3. Does the name of the app's folder change from /tce to /tcz when 2.4 is released?

Probably all this will be answered in the upcoming announcements you mentioned. Just wanted to get them on the list.

Extraordinarily cool distribution is TC. It is a pleasure to use.

Best Regards,

sci_fi

[roberts]

1. Yes. You should plan to migrate over to tczs.
2. Yes. A mix of tce and tcz both work in a single tce directory.
3. No. No names are going to be changed. Still use tce directory. Extensions will remain tcz

[philip]

It is important to note, that you are not losing functionality. Each tcz can be loaded into ram, just as the tce did.

Great. I like the security of booting from a USB key, then unmounting and unplugging the key so nobody can mess it up. When the time comes (later -- maybe in the release announcement), will you please include a couple of lines describing the format and function of the files tce/tcz2ram.flg and tce/tcz2ram.lst? This will help users like me make the next step. Thanks for everything.

[roberts]

As usual, perhaps I was too terse when such was announced for v2.3 in the change log:

* New tcz2ram.flg placed in your tce directory will cause all tczs to be loaded into ram.
* New tcz2ram.lst placed in your tce directory will result in those tczs specified in such be ram loaded.

You can start your migration to all tczs now.
If you wish all tcz2 to be loaded into ram, as current tces do then place the flag tcz2ram.flg in your tce directory. To make such a flag simply

touch /path/to/your/tce/tcz2ram.flg

If you are currently using a mix of tces and tcz then to move to all tczs with the same functionality then simply list each tcz in a simple ascii text file name tcz2ram.lst. Just use any editor to create/make/edit this file in your tce directory.

Note using appbrowser in v2.3, install button on a selected tcz not only loads to ram but also adds the selected item to tcz2ram.lst.

[robc]

If you are currently using a mix of tces and tcz then to move to all tczs with the same functionality then simply list each tcz in a simple ascii text file name tcz2ram.lst. Just use any editor to create/make/edit this file in your tce directory.

When listing these extensions does the actual .tcz need to be included or could I just put the extension name? i.e. cups instead of cups.tcz

[roberts]

The full name of the extensions and one entry per line, .e.g.,
glib1.tczl
gtk1.tczl

[florian]

a quick tip (that I discovered recently) for those who would migrate fully to tcz already today:
As of today there that are extensions that only available in the tce repo, not tcz. However you can convert those extensions to tcz : load the squashfs-tools extension and then invoke the tce2tcz.sh script which is included in the base.

[bigpcman]

As usual, perhaps I was too terse when such was announced for v2.3 in the change log:

* New tcz2ram.flg placed in your tce directory will cause all tczs to be loaded into ram.
* New tcz2ram.lst placed in your tce directory will result in those tczs specified in such be ram loaded.

You can start your migration to all tczs now.
If you wish all tcz2 to be loaded into ram, as current tces do then place the flag tcz2ram.flg in your tce directory. To make such a flag simply

touch /path/to/your/tce/tcz2ram.flg

If you are currently using a mix of tces and tcz then to move to all tczs with the same functionality then simply list each tcz in a simple ascii text file name tcz2ram.lst. Just use any editor to create/make/edit this file in your tce directory.

Note using appbrowser in v2.3, install button on a selected tcz not only loads to ram but also adds the selected item to tcz2ram.lst.

Are both the flag file and list file required for a "mix" of TCZs or just the lst file?

[roberts]

The flag means all tczs load into ram, whereas, the list lists only tczs to load to ram
Neither flag nor list means anything regarding tces. In a mixed environment the definitions do not change.

[bigpcman]

The flag means all tczs load into ram, whereas, the list lists only tczs to load to ram
Neither flag nor list means anything regarding tces. In a mixed environment the definitions do not change.

Perhaps a stupid question but I'm sure I will end up doing it. What happens if I forget to remove the flag file and end up with both a flag and list file in the tce directory. What will take precedence?