[ENHANCEMENT] Support a Debian User Repository (DUR?)
Closed this issue · 3 comments
In mpm's current state, it pulls packages from both the AUR and Arch Linux repositories.
This is all fine and dandy, but dependency name conversions can get tedious after a bit, and can break at a moments notice when the dependencies for PKGBUILD's change, resulting in a package that won't install.
A potential solution to this would to create an AUR platform for Debian distributions, probably known as the Debian User Repository (DUR; subject to change).
The biggest benefit that would be made out of this is no more worrying about dependency management. It would also ensure packages are aligned to work with the latest releases of Debian distros, with Ubuntu probably being the upfront due to it being the most popular of the bunch.
There's also a few things that I can't fix between Arch and Debian packages, such as with this issue. While I coud implement a workaround such as prefixing the version with a custom string, it's nothing but hacky at best, and doesn't work well in the long run.
The downside of this - all of the packages that would've been in the AUR now have to be recreated. The reason I have neutral feelings for this is that the dependency database already constantly needs to be filled, resulting in the packages needing to be "recreated" to work properly on Debian systems.
If I were to go the route of a Debian-like user repository, I'd throw it up on a aurweb instance, and attach the appropriate branding where needed.
I could potentially support both, but I think it would be wiser to choose one or the other.
One would definitely require less effort, and I'm just not sure if the other would be much more efficient, if at all.
Any thoughts on sticking with the AUR and Arch repos?
Update: I'm thinking of calling it the makedeb Package Repository (MPR) if I go the aurweb route.
Edit: I like the way Debian User Repository and makedeb User Repository flow off the tongue, but they look weird abbreviated, right? (DUR, MUR)
Any suggestions are also welcome.
Just adding some more comments on the matter:
The time it takes to actually get dependencies worked out, could just be spent making a PKGBUILD that 1, works natively, and 2, would be easier to maintain and manage in the long run.
It has now been decided that mpm will be taking on the route of using an aurweb instance specifically for Debian packages.
See the README as well as the docs for more info.