dCore Import Debian Packages to Mountable SCE extensions > dCore X86

is dCore idea applicable to other distributions?

<< < (2/2)

Jason W:
If a core made by files from a different distribution was paired with a directory of custom startup scripts and data like has been done with dCore, then it could exist.  The only advantage I see since Debian has everything would be possibly newer packages, and the startup scripts and data would have to be tailored to each different core for that distro.  I would personally rather the effort be channeled to dCore given the size of our development base. 

The main work with importing on the package end is in the custom startup scripts.  But given the vast array of packages that work in dCore with no invervention, there is the same or less need for startup script action with the imported Debian packages than there is with the standard custom compiled ones in /usr/local.

pioj:
Thanks!

I've been diggin into the scripts and I'm getting the idea.  Let's try the next theory:   8)

Imagine I'm able to add debian_jessie_main_i386_Packages, debian_jessie_main_i386_Packages.gz and debian_jessie_main_i386_Packages.zsync files to the current repo at:

http://repo.tinycorelinux.net/5.x/x86/

Then I modify debGetEnv script to point for those files instead of the Wheezy ones (that DEBINX variable).


.What would happen? 

roberts:
Of course, you are free to explore and share, but for now the goal is to make dCore move beyond alpha with the existing Debian repository and custom premade sces. So testing with that is mind would be most helpful and appreciated.

Navigation

[0] Message Index

[*] Previous page