Tiny Core Extensions > TCE Q&A Forum

Recursion of extension.dep files

(1/2) > >>

Kingdomcome:
I was curious about this topic while I was attempting to make a samba extension.  Now that Juanito has, I feel this question needs asking and answering.  When a new extension is made that depends on another extension, that depends on another extension, should the new extension.dep contain all dependencies an sub-dependencies? 
Looking at this from the other side, would it be possible to take the burden off of the extension makers to track down all sub-dependencies with a couple lines of code in appbrowser(?) to recursively check extension.dep files?
Not to point fingers or call out a great contributor with the example here, but when I downloaded samba today, the samba.dep only contains cups.tcel.  cups.tcel was downloaded, but the .dep was not, and therefore, the cups dependencies were not.  Choosing to download cups.tcel in the appbrowser did grab the dep file and satisfy the dependencies, but I feel an understanding of roberts' intentions and a standard remedy for this merits discussion. 

^thehatsrule^:
Simple dependency is used.  So there is no recursion at all.

The samba.dep should contain all the dependencies of the other extensions, so it should probably be listed as a TCE bug.

Juanito:
I forgot to include the cups dependencies in the samba dep file - thanks for pointing this out, I'll fix it shortly

Edit: It should be OK now

roberts:
Everything that I have done with Tiny Core is too keep it simple.

As such, the simple test for any extension and its required . dep file, is to boot tiny core with the base norestore options then load your extension. If you have a proper .dep file your extension will work.

Juanito:
It could be worth having tce-load list the extensions in the dep file as it loads them?

Navigation

[0] Message Index

[#] Next page