dCore Import Debian Packages to Mountable SCE extensions > dCore X86
dCore-5.0.alpha1 released
theYinYeti:
Thank you for the clarification Jason W.
Let me repeat: it is an awesome project! :-)
One thing I liked a lot about DSL, years ago, was that it was light enough to support my 24MB RAM Toshiba laptop, but I still could enable “Debian compatibility mode” and install packages from Debian Woody repositories :-p
Nice work!
vinnie:
--- Quote from: Jason W on July 01, 2013, 09:26:14 AM ---And dCore aims to support all core features, it simply draws on the Debian repo for it's extensions. But the extension installing/updating features of the TCZ are not all supported by the SCE, but that is partially due to the differences in package type.
--- End quote ---
So there are only sce extensions in dcore and not tcz?
roberts:
--- Quote from: bmarkus on July 01, 2013, 06:59:02 AM ---dCore-5.0.alpha1.iso
isolinux.cfg configured to load core.gz but there are no such only dCore.gz therefore boot fails.
--- End quote ---
Fixed on server for next iso creation.
roberts:
--- Quote from: vinnie on July 01, 2013, 11:24:33 AM ---
--- Quote from: Jason W on July 01, 2013, 09:26:14 AM ---And dCore aims to support all core features, it simply draws on the Debian repo for it's extensions. But the extension installing/updating features of the TCZ are not all supported by the SCE, but that is partially due to the differences in package type.
--- End quote ---
So there are only sce extensions in dcore and not tcz?
--- End quote ---
That's why sces are not just merged into Core.
dCore the 'd' is for Debian and also for different from Core.
no tcz support in dCore.
You may want to read http://forum.tinycorelinux.net/index.php/topic,14332.msg91108.html#msg91108
which explains why sce.
--- Quote ---The concept behind dCore is to more easily maintain the Core philosophy across many platforms without having to build and maintain many platform specific repositories
--- End quote ---
SamK:
Some unordered questions, simply in as they occurred to me.
Once an SCE app is imported is it possible to apply a security upgrade (issued by Debian) to an active dCore system, or is a rebuild of the SCE app required to incorporate it?
--- Quote from: Jason W on July 01, 2013, 09:26:14 AM ---...dCore aims to support all core features, it simply draws on the Debian repo for it's extensions.
--- End quote ---
As it draws on Debian Stable does this imply an app in SCE format inherits the same degree of app stability? Is it vulnerable to upgrade changes at an OS (dCore) level?
--- Quote from: Jason W on July 01, 2013, 09:26:14 AM ---The SCE has replaced the SCM, as it contains all it's needed dependencies in one file.
--- End quote ---
Does this mean an SCE app is resistant to breakage? For example is it vulnerable to SCEs created from custom packages that are not available via Debian? Is there any degree of sharing common dependencies in an SCE?
Can an SCE be managed a single entity? e.g. can it be removed (not unloaded/uninstalled) from a system as a single unit in a similar manner that an SCM was? How do a user do it?
Have any tentative comparisons been done of RAM usage for similar SCE v TCZ systems? If so the figures might be informative.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version