Installer extensions

[yiyus]

Is there a standard convention on how to create installer extensions similar to firefox-latest? I am using a similar approach for a plan9port extension. The final extension weights more than 100MB, but can be compiled without more dependencies than compiletc (and squashfs-tools to create the .tcz). I would like to know if there are any guidelines I should follow.

In fact, I have not even been able to find which is the common procedure for extensions creation. I have read the guidelines, the wiki page, and have found tcztools and other similar tools, but as far as I see there is not some kind of repository where I can get "source packages" of extensions. I am guessing all the packages in the repos (or at least most of them) are not recreated by hand in an ad-hoc basis each time they are updated. How is this normally managed?

There are many solutions for this, like FreeBSD ports or Archlinux PKGBUILD files, or even plain Makefiles or a dedicated tool like tcztools. I am a newcomer to this community and I don't intend in any way to tell you how to solve this problem, I am just trying to find out if there is an established way before taking my own. Once I have a clear picture, I will be glad of updating the wiki.

Thank you!

[gerald_clark]

No, there is no standard for package creation.  Package sources are in the download area.
If you don't  see the source it probably has not changed since the previous release, so look in the download area of previous releases.

[Rich]

Hi yiyus
Source packages are in the  src/  directory under  the  tcz/  directory in the repositories. For example:

Code: [Select]

http://tinycorelinux.net/4.x/x86/tcz/src/
http://tinycorelinux.net/5.x/x86/tcz/src/
http://tinycorelinux.net/6.x/x86/tcz/src/If you need to get to TC2 or TC3 sources:

Code: [Select]

http://tinycorelinux.net/2.x/tcz/src/
http://tinycorelinux.net/3.x/tcz/src/