Recently i tested several apps for which only .deb files were available.
I used debtab for this.
When i checked the .PKGINFO before the final package build, i found some dependencies, that on the second look doidn’t make much sense. Like for instance brave-bin for an audio app.
The person providing the .deb says that dependency is not in their .dep.
So i unpacked the .dep and searched it. I found “depends” in a file named control, and there was no reference to brave-bin.
This is just one example. In another case, there was Davinci Resolve as dependency.
So what is going on here?
Does debtap miraculously create unnecessary dependencies?
If so - why, how?
Any ideas, clues?
Hard to believe that the AUR doesn’t have something that Debian does? I’m sure it’s possible, but has to be an edge case.
Edit: I’ve ran debtap exactly once, I don’t remember how well it worked out for me though. I would hesitate to do it again.
Thanks, that’s all nice and dandy. Avoiding probs is always a good idea / advice.
But because i actually ran into a prob, i posted here in hope for some help to find a solution …
I’m not a coder, and am not on git, so i can’t ask the debtap guy myself.
Also i read about making a PKGBUILD - but i don’t know how to do this, in case of a .deb source. Debtap seemed to be the way to go at first. After my test results i’m not so sure about this anymore.
The packages in AUR might have flaws or probs too, as it is not advised to trust them blindly. Or am i mistaken here?
However, the AUR is in a native packaging format adapted to the ecology of Arch, vs witchery to try to shove a deb into the digestive system, which could result in flatulence
