The Tinycore repository is a bit... well, poor

[Alby]

I really like the Tinycore philosophy, and I look forward to using Tincore extensively in the future. But, for now, I have mixed feelings about adopting it as my main operating system.
My misgivings are mostly about the scarce availability of extensions.

Would it not be possible to adapt the Tinycore extension system to something more mainstream (for instance the Arch Linux repository), so that we could have access to about every program we may need?
I know that this is not a small request, because it would entain a radical shift in the system, but I really believe that the priorities need to be reconsidered.

Being hampered by the lack of software is not only a nuisance, but something that drives people off, because there is nothing more frustrating than needing something badly and knowing that on other distros it easily available.

So, my proposal would be: could we not try implementing a package management that relies on more mainstream packages?

Thanks for your comments

[bmarkus]

I'm happy with TC'c actual extension management. One reason why I'm here its independence. Also, hate 'based on u..., based on d...' distros.

If you are not happy

- go and use the upstream distro with its own repository
- contribute to TC repo with missing package

[Guy]

Tinycore is different to other operating systems. One of the differences is that (when installed frugally - the default way) the apps are read only. That is the files in the apps cannot be modified. Settings can be saved, the the apps cannot be modified. With most other operating systems, files may be modified.

This means that, under normal circumstances, if Tinycore works first time, it will work every time. The filesystem does not become corrupted.

As a result, you can't install apps from other distros.

However, apps from other distros can be converted to Tinycore extensions. Then they could be installed. Anyone doing this would also need to convert all dependencies.

There is a script somewhere in this forum for converting Debian (.deb) apps. If you search, you should find it.

A similar thing could be done with .rpm apps.

Don't expect the Tinycore team to start converting apps from another distro.

However, if someone wants to make a new distro, they could use the Tinycore base, with a script for converting apps from another distro. This would not be a small task.

Puppy Linux can use apps from a number of different distros.

[bmarkus]

However, apps from other distros can be converted to Tinycore extensions. Then they could be installed. Anyone doing this would also need to convert all dependencies.

There is a script somewhere in this forum for converting Debian (.deb) apps. If you search, you should find it.

A similar thing could be done with .rpm apps.

While it may work, do it only for your personal use. Programs in the repo are compiled for TC for example to run on old CPUS's as a policy. There are no guaranty that it is true for alien binaries. Also, programs usually have many options to add or remove features. You must consider TC environment not just move it from one system to other.

Keep TC itself clean.

[Alby]

Your replies provided a partial solution to my problem, with the suggestion that .deb and rpm packages can be converted to TC extensions. This is very useful and goes a long to way in alleviating the problem. However, if the conversion process via the script is not always guaranteed to succeed (as bmarkus pointed out), then the problem still remains, at least for non-advanced users like me. My expertise being rather limited, I would not be able to manually convert the alien packages to TC, and I am afraid I may not even be able compile from the sources safely.
If indeed the TC team does not undertake the task of providing a minimum amount (which has not been reached yet, IMHO) ready-to-use extensions guaranteed to work well with TC, then I am afraid that many users will find it hard to stick with TC, and it would be a pity, because TC is excellent.
Please, do not take my remarks as a criticism, but as a request and an encouragement.

I wish the developers team could dedicate some more time to porting applications, for the benefit of users like me who are unable to do the porting themselves.

[Juanito]

I wish the developers team could dedicate some more time to porting applications, for the benefit of users like me who are unable to do the porting themselves.

Why not read the section of the wiki on making extensions and have a go yourself - several users have tried this and received help from the forum members when stuck.

[bmarkus]

I wish the developers team could dedicate some more time to porting applications, for the benefit of users like me who are unable to do the porting themselves.

Model is different, extensions are provided by community not by dev team.

[curaga]

I wish the developers team could dedicate some more time to porting applications, for the benefit of users like me who are unable to do the porting themselves.

We do, but we're mostly at the point where everything we use ourselves is there. While we could build $APP_X, and sometimes do when requested, not using the app does make it harder to properly maintain an extension.