dCore Import Debian Packages to Mountable SCE extensions > dCore X86
importsce "add-on".sces based on "base".sces
Jason W:
First, I appreciate any and all interest in dCore and I don't want to come across as defensive or dismissive in the presence of new ideas or requests. I also think it would be useful if there was an option that reduced duplication among sce packages.
How it is now is basically like PC-BSD, all dependencies are in the package file which is quite large, but only what is not already installed is merged into the live directory tree.
I have some ideas in this direction I may can prototype, I will think more on it.
thane:
I admit to being in over my head here, but my understanding is that it takes a lot of effort on the part of developers to maintain the Tiny Core tcz repository, not only to package apps as tcz's but to make sure all the dependencies are in sync etc.
I thought an advantage of dCore is that less of that is required. Since each app is packaged separately with its own set of dependencies (regardless of what's packaged with other apps) there's a lot more flexibility in obtaining apps from other repositories and having them work in TC. Not only a lot more apps but less effort needed from developers.
Is this wrong?
Jason W:
Thane - that is correct. However I have made some adjustments to importsce and the related files that will allow the use of existing sce's as dependencies. Like the size listing option, it will not affect those that want to stay with the current self contained sce. This option would make expanding one's sce collection much more efficient, of course the current routine will remain the same.
Say you have a huge mydesktop.sce that contains all of the deps of gthumb. Use the following command to make use of mydesktop.sce as a dependency.
importsce -d gthumb
With the -d option, you will be prompted with a select menu listing existing sce's in your sce directory. They don't have to be mounted. Select mydesktop as a dep, then proceed. Multiple dependencies are possible.
The result is that gthumb.sce will contain only the gthumb package if all the required deps exist in mydesktop, that is checked for by the list of debs that mydesktop.sce is made of against what gthumb requires. A gthumb.sce.dep file is created, containing mydesktop as the entry. If loadsce sees a sce.dep file when loading, it will check the needed debs versus what the sce in the dep file consists of, alerting the user if the required debs are no longer in the mydesktop.sce. Just in case one updates mydesktop.sce and removes packages on re-creation of it. That way, no mysterious brokenness, missing required packages will be echoed.
I have the code in place and will test more this evening.
netnomad:
hi jason w,
great news... i'm looking forward and help testing :)
thank you for your commitment.
yoshi314:
--- Quote from: Jason W on February 25, 2014, 03:48:00 PM ---The result is that gthumb.sce will contain only the gthumb package if all the required deps exist in mydesktop, that is checked for by the list of debs that mydesktop.sce is made of against what gthumb requires.
--- End quote ---
What will happen if there are some dependencies missing? Will they be included into gthumb, or will a rebuild of mydesktop.sce will be required?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version