![]() ![]() It is even described in the buildscript template that you should not care about cleanup, quote: cleanup is not performed. Every buildscript is started on a fresh Slax operating system. As soon as the module is ready, it is uploaded to Slax server and the virtual machine reboots, effectively losing all modifications. Those machines get instruction to run your buildscript in order to produce the module binary file. At the server side, there are several virtual machines with Slax running. In general, it doesn't matter what files are left in the system after your buildscript ends. At the moment you should be able to use auto* keyword (with asterisk at the end) to match automoc4.Ĭleanup is not necessary. So if you search for 'auto' and you get 50 modules while you're looking for 'automoc4' only is not ideal. The problem is that if there are too much search results, it may be confusing. I will try to improve the search capability. So what is the correct way to handle this situation? I see now, that in the system-settings is only oxygen theme. I had to adjust the buildscript to copy those icons from hicolor theme to the oxygen theme. For some reason, the icons installed to /usr/share/icons/hicolor weren't used/found. Is it correct that way? Or is it better to not delete the files? (maybe to reuse them for next build, but it would gradually use a lot of space on the build server) Because when I wrote the buildscipt I checked a few another buildscipts and the cleanup sections were empty.Īnd lastly, after my module was created, the application and KDE menu were missing icons. I put there commands for removing the temporary directories and files (source code etc.), so after the buildscript is finished, there remains only the buildscript and the created module. Secondly, I have a question about the cleanup part of the buildscript. the modules section was recently updated and is far better, so thanks Tomas for that! So this is suggestion for Tomas to make the search better, if there's time -). ![]() Only to realize later, that the automoc4 module is already there. I searched for "auto" and when there was no automoc in the results, I wrote new buildscript for it. One thing surprised me, when I found out I need automoc4 tool to compile the source code - the web search for modules isn't "fulltext". I decided to write a buildscript and make my own module for kshutdown. module page for kernel-firmware and module page for b43 broadcom wifi firmware B43 firmware is a special tiny package with only broadcom wifi firmware drivers. Kernel firmware is somehow big and bloated, contains lots of fw drivers from many sources. Once you do, those blocks disappear, and put off slightly your inevitable demise.Īnd finally, firmware drivers, you probably know them, those are important if you wish to use some hardware which doesn't have the driver included in Slax natively. ![]() To eliminate blocks from the stack, line up at least three of one color, horizontally or vertically. ![]() Slowly, your stack of colored blocks grows from the bottom, and you've got to make sure it never reaches the top. In a style similar to the original Super Mario games, featuring 9 enemies and 26 playable levels, supertux game ensures long lasting fun.Ĭrack Attack is roughly based on the Super Nintendo game Tetris Attack. SuperTux is a classic 2D jump'n run sidescroller game. For today, I've selected two games, two office packages and some firmwares.Ībiword is a word processing program similar to Microsoft Word.Ī GNOME spreadsheet app, similar to Microsoft Excel. I'm going to publish few words from time to time about interesting modules made for Slax. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |