Tiny Core Extensions > TCE Talk
New package manager
wysiwyg:
--- Quote from: Leee on February 01, 2026, 06:15:02 PM ---
--- Quote from: nick65go on February 01, 2026, 05:14:19 PM ---It seams that TC developers think that users initially search for apps, then users settle with some apps and updates seldom.
--- End quote ---
That's pretty much what I do. I have recently started doing occasional extension updates but I haven't exactly made a habit of it.
--- End quote ---
In a future version pax will have the ability to alert and/or automatically perform this task. I just needed to iron out what needed to be done beforehand. Most people don't do updates if they don't know they are available. Actually most people don't install updates even when they're told they have them. This is obviously unsafe and leaves you subject to exploits...
Leee:
I follow the forums here pretty closely, so if there's an update to an extension I use, I'll usually know about it that way and update as needed. Not a big fan of automatic updates in general.
That's not say I;m not interested in pax - but at this point it's really just a curiosity to me.
wysiwyg:
I completely understand. I'm also not a big fan of automatic updates (which is why I didn't mandate them in pax). To me freedom is better than anything. Although freedom comes with responsibility. If the user chooses not to update their system, then the consequences fall on them.
I do appreciate your curiosity for the project, and look forward to hearing any feedback you can provide. I want the software to be as useful to people as possible, of course.
nick65go:
looking into https://github.com/cliquesoft/pax/blob/main/bin/pax it seams it is a /bin/sh script, which is OK.
- An 'html' output option: it needs a "small browser" to see this output (you can be inspired by how fluff.tcz shows its help)
- A graphical interface: FLTK is in the base. [not GTK1/2/3 neither QT4/5/6. nor Xdialog when Wayland is the future].
As https://mirrors.dotsrc.org/tinycorelinux/17.x/x86_64/tcz/pax.tcz.tree shows, pax depends on "many" other tcz
--- Code: ---pax.tcz
coreutils.tcz
gmp.tcz
squashfs-tools.tcz
liblzma.tcz
lzo.tcz
libzstd.tcz
liblz4.tcz
--- End code ---
The package-manager belongs in the base, the base must / should be small, but pax+deps is not small size for now by "TC developers standards". Maybe I am wrong, but I know how hard / long was the discussion on TC boot / config parameters: a 4 byte file (containing just a boot option as text) have 4KB (a page) in RAM etc.
I wish you success, because I want TC to evolve. From my point of view the "libs dependency hell" was solved by an AWK engine or can be a C-compiled software (like in Arch-linux or Alpine-linux ). Maybe your focus is in download speed, or parallel sources; where is the bulk CPU consumption, in server or client, etc. I mean do you want to "protect" the web-server energy/bandwide by transferring the energy bill to the client-user, etc. I just ask...
If I may: It will be nice to define first what you improve (in Tinycore!), to measure what we have already (for a common user) and then you state by how much you WANT (not necessarily to achieve for now) to improve (in KB size, KB/second, or % or whatever).
nick65go:
I am a novice in terms of software licensing. But I saw that "pax" has a "Cliquesoft Public License [CPLv2]".
I try to do not agree / obey (shame on me) with IP (intellectual property, aka new feudalism), the only acceptable license is something like this https://landley.net/toybox/license.html ; YMMV
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version