Tiny Core Base > Release Candidate Testing
Core v7.0beta3
Juanito:
How about:
--- Code: ---if [ "$(version | sed 's/\..*//')" -gt "5" ]; then
--- End code ---
?
Edit: updated extension posted.
Juanito:
--- Quote from: coreplayer2 on February 03, 2016, 05:19:58 PM ---notice the direct loading error and resolution if loaded from /usr/local/lib/firmware/
--- End quote ---
I'd assumed that message occurred when the kernel driver did not contain the firmware (a la broadcom wl), but no, I don't think it's a problem.
curaga:
@coreplayer2
Usually if the firmware is not available the first time, the driver will print a message and exit. Then if the firmware is loaded later, the driver will try to load again, and this time succeed, like in your dmesg. So in practice, the message is the only difference.
@dentonlt
Clearly a bug/suboptimal behavior somewhere, most likely in gcc. Though the official build didn't grow at all, the added 100kb or so came from new options.
If you want to, you could go trying different gcc versions, and if it still happens in the latest 5 series or 6 git, report to them and isolate what caused it.
andyj:
I used -ge "6", but -gt "5" works too. :D
While we're on the subject of beta testing, I would like to make a proposal: In theory the extensions are supposed to have a copy of the license available. Technically this doesn't mean that it needs to be _IN_ the "some-xyx-extension.tcz" file, but that it be available _WITH_ the file. In my cursory scan of many of the extensions available I noticed that the license files are lacking. Rather than repackage them to be in compliance, I propose that we create a new file with a name such as "some-xyz-extension.tcz.lic" to compliment the existing files which would have the text of the license in it. Because the license file names can vary based on the type of license itself, this would standardize that. I say beta test because this suggests that a new "License" tab be added to the app browser and that the license be downloaded with the extension, so there would need to be a few strategic code updates. Thoughts?
Juanito:
Note that the license for all of the extensions will be in the source tarball in the repo src folders - apart from licenses which expressly state that they should be in the extension itself, they are already available.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version