Hi! That honestly does change how I'd like to do everything in the future. I'm much more familiar with Python than PHP, and being and to do things in Python would make things significantly easier on my end (in which case I'd be fine holding off for quite a bit).
we are most likely going to be major version bumping the project when the Python/FastAPI port is complete
Is this something you (or anyone else on the aurweb team) would be looking for help with? I wouldn't say I'm the most strongest person with Python (I start hacking with using it just a couple weeks ago), but I have (I think) caught on relatively quickly [1] for the short burst of time I've been using it. If I were to start contributing, is there anywhere I could start? I'm thinking most of the changes would be in the 'web' folder (I saw most of the PHP files were there), but I was curious if anything might've been wanting to get done first or anything like that.
Is there a location of the "MPR" source I can look through? I'd like to check out how you're modeling your code off of what's in aurweb so I can help better.
You can find the current source for the MPR in the footer of this email [2]. Ignore the notes in the README about mprweb perodically using releases of aurweb though, as that was the plan before I was thinking about making any heavier changes to the platform.
[1]: https://github.com/hwittenborn/tap
[2]: https://github.com/makedeb/mprweb
---- On Tue, 20 Jul 2021 15:40:48 -0500 Kevin Morris via aur-dev
This email is in reference to an issue on the Arch Linux bugtracker: https://bugs.archlinux.org/task/71427
---
I'm currently working on a platform known as the MPR [1], which is quite literally the AUR, just designed for Debian-based distributions. The whole idea of the project builds upon makedeb [2], which actually uses makepkg, and does some conversion stuff on top to make the package work properly with APT.
Getting back to the MPR then - I was wondering if it would be possible to get a new release published. The current 5.0.0 release has some bugs that aren't present in the live version, and it's requiring me (as stated in the issue on the bugtracker itself) to try to triage these bugs manually (which isn't too much of a problem, but for the reason mentioned next, it would be easiest if I could just get a new release with all the fixes incorporated).
The MPR is currently running off of mprweb [3], which (at this point) is pretty much just aurweb with a reskin.
I'm wanting to start make some more heavy modifications to the platform though, such as adding some things to the RPC JSON interface (mostly for things mentioned in makedeb's docs [4]), and possibly doing some things with the GUI. At current, the goal is to get a release of aurweb, and then just fork it and go from there. I wouldn't be using any new releases of aurweb at that point, and would just keep adding in features as I go along.
If I were to make any changes that would be deemable to be contributed back to aurweb, I'd be more than glad to do so as well. I'm just wanting to, before I start any (objectionably) bigger modifications, be able to use something that's at least somewhat close to aurweb's current state.
I'm not asking for anything immediately, I'm just, again, wanting something where I can have a starting point where these known bugs are just polished out.
[1]: https://mpr.hunterwittenborn.com/
[2]: https://github.com/makedeb/makedeb
[3]: https://github.com/makedeb/mprweb
[4]: https://docs.hunterwittenborn.com/makedeb/makedeb/additional-pkgbuild-specs
---
Hunter Wittenborn
-- Kevin Morris Software Developer Identities: - kevr @ Libera --- Hunter Wittenborn https://www.hunterwittenborn.com https://github.com/hwittenborn