Menu entries, icons, setup scripts, .info and .dep files

For graphical applications, or front-ends to command line applications, you might want to add an icon, a menu entry, or both. An info file is needed for all extensions, if they will be submitted; a .dep file is also required, if your extension always requires some other extensions to run.

These are added to the submenu “Applications”, which is empty by default. Entries created automatically by the system at the time extension loaded, based on freedesktop.org compliant menu definitions (.desktop files) in

/usr/local/share/applications

directory provided by the extension.

When an extension is loaded, an executable file of the same name as the extension in /usr/local/tce.installed/ will be called, if it exists. This is optional.

For details see Adding Custom Startup Scripts section in the Wiki.

They are named like the extension, with .info added, for example kmaps.tce.info. Use all parts, even if your extension does not match; in that case, put n/a for example to the unneeded field. Please do not forget a proper description of your software! An example .info file:

http://www.tinycorelinux.net/files/3.x/tcz/ace-of-penguins.tcz.info

Tinycore handles dependencies only when using tce-load or the graphical appbrowser to get extensions from the repository, both when installing and only downloading. The .dep files have no effect for manual downloads, or local extensions. It's named as the extension + .dep, for example extension1.tcz.dep.

For dependencies, there are recursive resolutions (implemented as of version 2.10). Previously, the extension would contain the full names of all extensions it depends on, and all they depend on. This previous method is still compatible, but the recursive approach is the current standard.

The format is one extension per line with no empty lines. For example, an extension.tcz.dep might have:

b.tcz^ where a.tcz.dep might contain