Complete the port of flatpak to appstream from appstream-glib
a project by ldragon
Updated over 2 years ago. 1 hackers ♥️. 1 follower.

Project Description

Currently flatpak uses appstream-glib to parse and generate appstream files however, appstream-glib is no longer maintained and this has resulted in many features not being propagated to flatpak. There is currently 2 prs porting flatpak & flatpak-builder to appstream.

Goal for this Hackweek

The goal would be to finish the last mile and ensure that the repo's produced and 1:1 or at least close enough to complete the switch.

Resources

https://github.com/flatpak/flatpak/pull/4904

https://github.com/flatpak/flatpak-builder/pull/418

Join this project

Looking for hackers with the skills:

flatpak c appstream

This project is part of:

Hack Week 22

Activity

  • over 2 years ago: ldragon liked this project.
  • over 2 years ago: ldragon added keyword "c" to this project.
  • over 2 years ago: ldragon added keyword "appstream" to this project.
  • over 2 years ago: ldragon added keyword "flatpak" to this project.
  • over 2 years ago: ldragon started this project.
  • over 2 years ago: ldragon originated this project.


    • Comments

    • ldragon
      over 2 years ago by ldragon | Reply

      Implemented and prs have been sent upstream (flatpak and flatpak-builder)

    Similar Projects

    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources