Tiny Core Extensions > TCE Talk
Requests for extensions
Juanito:
I'm not totally sure I see the difference between using app-browser to get extensions and using package mangement (apt-get, yum) in a full distro?
dsl had some libs that were the same as debian woody, some libs that were more recent than debian woody and (perhaps) some libs that were the same as debian serge. This meant that apt-get/dpkg would work cleanly sometimes, but more often than not, things had to be forced because of the lib mis-match with unpredictable results.
I believe I'm correct in saying that the initial compile environment in dsl was made from debian packages and, as such, sometimes gave strange errors - this was the initial driver for the compile-3.3.5 extension, which was built on dsl using the same libs as dsl and is the reasoning behind the compiletc extension.
I may be wrong, but I don't think apt-get or similar makes sense with tc (and it would certainly be a lot of work) - there is however a lot of learning/satisfaction to be gained in compiling your own extension and making it available to others :)
tobiaus:
--- Quote from: Juanito on January 08, 2009, 02:30:41 AM ---I'm not totally sure I see the difference between using app-browser to get extensions and using package mangement (apt-get, yum) in a full distro?
--- End quote ---
just the sheer breadth of the repository:
sudo apt-get install mped works, sudo /usr/bin/tce-fetch.sh mped tce doesn't. when you make a request for something already available in apt as a tce, you are at the mercy of your own compile environment and the generosity of wonderful contributors like yourself. i am not naive about the practicality of adding apt to tc. i'm sure it's entirely impractical. a nice thought, but an idle one. i'd love for you to disagree.
--- Quote ---there is however a lot of learning/satisfaction to be gained in compiling your own extension and making it available to others :)
--- End quote ---
no, i disagree. i think compiling is one of the least straightforward, most unpleasant linux tasks there is, next to installing a printer or configuring wireless. i always avoided it, up until tc gained so much trust i tried with a few simple program sources. not only did it not work, i have no idea why and there seems to be no idiot's guide anywhere.
you're entitled to your opinion and it's a good thing for all of us it's different, but it's not for the average user that thinks tc is generally friendly enough.
i did compile one package in tc today: zile, based on roberts's book. first compile ever (yay!) then i tried mp from triptico.com. it said it couldn't find ncursesw, oh well. but it's not fun at all. using tc is. apt-get spoils you. everything is already ready already. if compiling was just tedious, that's one thing. it's actually somewhat painful.
Juanito:
--- Quote ---it said it couldn't find ncursesw
--- End quote ---
if you look in the linux-from-scratch ncurses section, it explains how to get around that ;)
latte:
--- Quote from: tobiaus on January 08, 2009, 03:17:55 AM ---
--- Quote from: Juanito on January 08, 2009, 02:30:41 AM ---I'm not totally sure I see the difference between using app-browser to get extensions and using package mangement (apt-get, yum) in a full distro?
--- End quote ---
just the sheer breadth of the repository:
sudo apt-get install mped works, sudo /usr/bin/tce-fetch.sh mped tce doesn't. when you make a request for something already available in apt as a tce, you are at the mercy of your own compile environment and the generosity of wonderful contributors like yourself. i am not naive about the practicality of adding apt to tc. i'm sure it's entirely impractical. a nice thought, but an idle one. i'd love for you to disagree.
--- Quote ---there is however a lot of learning/satisfaction to be gained in compiling your own extension and making it available to others :)
--- End quote ---
no, i disagree. i think compiling is one of the least straightforward, most unpleasant linux tasks there is, next to installing a printer or configuring wireless. i always avoided it, up until tc gained so much trust i tried with a few simple program sources. not only did it not work, i have no idea why and there seems to be no idiot's guide anywhere.
you're entitled to your opinion and it's a good thing for all of us it's different, but it's not for the average user that thinks tc is generally friendly enough.
i did compile one package in tc today: zile, based on roberts's book. first compile ever (yay!) then i tried mp from triptico.com. it said it couldn't find ncursesw, oh well. but it's not fun at all. using tc is. apt-get spoils you. everything is already ready already. if compiling was just tedious, that's one thing. it's actually somewhat painful.
--- End quote ---
Hi again all.... :)
Thanks for your comments! Argh, I have to admit that I'd forgotten that tc ran in RAM, so that would indeed be a restriction (as tobiaus mentioned).
Yes, my main reason for thinking of an apt extension was just the sheer size of the Ubuntu (and Debian) repos, as mentioned above.
Going off-topic for a moment.... One thing I'd love to see in a small distro is a port of OpenBSD's pf firewall to Linux, but *that* would take a humungous amount of work, I imagine.
As I understand it, the underlying security infrastructure is quite different in OpenBSD and Linux.
I believe pf is superior to the existing Linux firewalls, but due to the difficulty of porting it to Linux, I guess we won't be seeing it on Linux any time soon.
curaga:
A big downside in apt would be that to install anything it would first install ALL ubuntu/debian base libs. Thus downloading in practise several hundred MB to your ram. In the process also borking most if not all TC libs, which could stop many apps from working.
If looking for a light ubuntu, do the server install, and only apt-get stuff that you use.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version