dCore Import Debian Packages to Mountable SCE extensions > dCore x86 Imported Extensions

sce-import modification

<< < (2/3) > >>

Misalf:
Just dropping my two cents.
I haven't yet tried dCore. Even though I find the combination of Core's extensions management and Debians repo quite appealing, I'm quite limited when it comes to downloading from the internet.
If I get it right, there is much more network traffic involved when is comes to installing, downloading or updating extensions on dCore.
I understand the performance problem regarding big numbers of extensions, even on default Core, and I try to workaround this by using initrds containing the extracted extensions I'd load anyway. Didn't tried to combine TCZ extensions yet but that might be an option as well.
If, maybe one day, dCore provides a similar extension structure as default Core, I'll be happy to hop in the boat.

ulfr:
   hi misalf

   having a combo sce automatically downloaded from debian is awesome 
 
   in addition
   i have found it is easy to make an extension that can function as both a tcz and a sce
   the only thing that is needed for it to be an sce is the md5sum file and naming it sce
   the only thing that is needed for it to be an tcz is the deps file (if needed) and naming it tcz
   i tried it with very simple tcz/sce first
   e3 which has no deps
   and then gtkedit which only has gtk1 and gtk1lib as deps (cant remember the exact names now)
   its very useful because you can make the exact extension combo you want
   and then load them when and if you want them in either tinycore or dcore 

   you might try this for fun

   i would also like to thank whoever writes the wiki
   its great having such fantastic documentation

   ulfr

Jason W:
After some very detailed examining of the code and features of the sce format, it has become clear to me that we can't weave in a modular option as the changes would be like starting over and then the bug testing and fixes, etc.  Things are very stable now, and I wish we could have this option but it appears we need to stay the current course.   It was worth considering, and thanks for everyone's input.

ulfr:
 
  thanks Jason

  for what its worth i agree
  dont mess with a masterpiece

  the way to introduce compatibility between the 2 systems
  is by making a handmade sce/tcz
 
  and thanks again for your awesome system 
  dcore and tinycore are the greatest

  ulfr

nitram:
Glad you find the dCore wiki useful ulfr. IIRC forum member sm8ps laid the wiki groundwork, others provided minor contributions, i've been the primary contributor for the last few months. There's only a few more things planned then most of my wiki work will be done. Please let me know if there are new topics that would be useful. Feel free to contribute too if you wish. All contributions welcome, even if just posting a dCore screenshot, documenting system specs and any special installation tips in the installation section or adding newly trialed software to the desktop applications section,

Just wanted to clarify some things that may help potential dCore users. Converting *.tcz to a dCore *.sce is easy, the other way around not so much. Would be nice if dCore could be used as a tool to build complex packages to use in Tiny Core but it's not that simple. TC is still the leanest but dCore builds complex extensions with ease that would typically be very difficult to build in TC (missing dev files, wrong package versions, multiple dependencies, uncooperative build scripts, etc).

Using the sce-import -d or -l (dependency or list) options greatly minimize duplicate dependencies between extensions, outlined in the advanced extension management section of the dCore wiki.

Regarding bandwidth, dCore starts with a small base like TC. When importing extensions the *.deb files remain archived on the system, unless purged by the user, and remain available for update re-imports or importing new extensions. So once a system is built the only downloads required are base file system updates (~13MB following RC release), updated *.deb files only (not the entire SCE extension library) and the DEBINX (Debian index database files few MB). The extension update process is CPU not download intensive. During updates there are usually only a couple/few *.deb files that require downloading at a time, similar to TC. The CPU just needs to rebuild the SCE using a combination of the newly updated and archived *.deb files.

To save bandwidth a dCore user could run stable release, install leaner software, stretch out SCE update checks (eg. monthly vs weekly), use import -p (preserve) to avoid updating DEBINX between every import and minimize purging *.deb files.

Misalf if you ever have extra bandwidth give dCore a try, your feedback and expertise would be appreciated for testing, bug fixes and enhancements :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page