Google Summer of Code with KDE
Hii everyone, one more month is passed and FwupdBackend is one more step closer for completion. In this past month, I have implemented following this:
#1 Firmware Updates Section is Now Cleaner: I have removed the unnecessary things like review backend, and screenshots which are not applicable for these updates. Also now the icons are decided based on the type of device.
#2 Refresh Remotes is now implemented: Now the metadata of enabled remotes are updating. Currently, the frequency is set to 30 days. These refreshing is like apt-get updates in Ubuntu based systems but for fwupd. The metadata is downloaded into cache directory of discover and then these files are sent to fwupd-daemon. In the attached screenshot you can see the downloaded files in the cache directory. The checksum is downloaded first and if it’s unchanged then only the new file is downloaded.
#3 Updates are shown on the updates page: The firmware updates are now shown in the update page of discover with all other updates. These updates are categorizing in “System-Updates”. These changes can be seen in the attached screenshot. (Missing string, please see the note!)
#4 Added Remotes Setting and EULA: Now the remotes can be enabled and disabled in the setting menu of the discover. If the user is enabling the remote then, he has to accept the EULA provided by LVFS. Additionally, the user also requires the root password to enable/disable it. I have also removed the unnecessary options like adding a new remote. Also, for now, I have disabled deleting the remotes.
#5 Testing Installs on Real Devices: Since I haven’t received the device, I still have to wait to test the code. The code for install is written, but it needs regress testing and improvement.
The Updates shown in the above screenshots are purposely put to visualize the code! I don’t have a device which supports firmware updates by LVFS
Development Branch here!
Targets For Next Month:
- Implement the Notification class.
- Check the install code on real devices
- The unit tests need to complete.
FeedBack Feel free to write comments below!