Maquis196
Member
Afternoon all, long term lurker and someone who has both pandora and pyra and wanted to share some thoughts.
I do apologise if this has been spoken about elsewhere but as someone finally getting software onto my pyra I am thinking about this, and ftr, I'm a devops by trade so I see pipelines config-as-code everywhere!
So basically I understand why we have the .dbp/.pnd files, and I get the whole "shop front" experience from the pyra repository, but I recall from the pandora days that someone would almost "grab" an application and upload their version and if they then dropped off the radar, we'd end up with multiple versions of that application and/or it was never updated.
So I'm wondering why we don't have a more "Gentoo/FreeBSD" type system where each app is in a git repo somewhere, patches/versions all handled there. When updated some pipeline somewhere releases a new dbp/pnd/deb release and then each software version can be bumped by anyone and then approved by someone to make it live?
Or say like how they have it on the MisterFPGA cores where each core is its own repo and then when updated, it releases the new file for people to download (plus maybe automatic updating of the pyra repo also?).
So yeah, apologies again if this has been discussed elsewhere, but im genuinely curious? Or would anyone be interested in something like this going forward?
I do apologise if this has been spoken about elsewhere but as someone finally getting software onto my pyra I am thinking about this, and ftr, I'm a devops by trade so I see pipelines config-as-code everywhere!
So basically I understand why we have the .dbp/.pnd files, and I get the whole "shop front" experience from the pyra repository, but I recall from the pandora days that someone would almost "grab" an application and upload their version and if they then dropped off the radar, we'd end up with multiple versions of that application and/or it was never updated.
So I'm wondering why we don't have a more "Gentoo/FreeBSD" type system where each app is in a git repo somewhere, patches/versions all handled there. When updated some pipeline somewhere releases a new dbp/pnd/deb release and then each software version can be bumped by anyone and then approved by someone to make it live?
Or say like how they have it on the MisterFPGA cores where each core is its own repo and then when updated, it releases the new file for people to download (plus maybe automatic updating of the pyra repo also?).
So yeah, apologies again if this has been discussed elsewhere, but im genuinely curious? Or would anyone be interested in something like this going forward?