You are not logged in.
See above. Any chance to get rid of such a dependency in the future?
I am aware it's makedevdep. And I don't mean Arch community is responsible.
Just some people might know more, than me about any attempts to get rid of mixing
p2 and p3.
Thx
Last edited by lefsha (2018-07-14 17:04:37)
Offline
makedepends != depends
Offline
makedepends != depends
I knew it. It was just an example. I just wish to know, whether any plans existing
to get rid of mixing both, currently it's not really possible. One or another package
push you to install both. Or at least there should be a tool to translate a code from
2 to 3. It's a terrible situation lasting too many years.
Offline
That's really up to the package maintainer, so there's nothing to "plan". I agree that split python2/3 packages in AUR are annoying and don't make much sense, but others seem to think differently.
Offline
I don't see the problem, makepkg -sr will remove python2 when you're done with it and split packages greatly reduces the maintenance burden.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
How comes you ask this nonsense on the forum?
You're unhappy w/ a PKGBUILD, ok.
Bad news, 50% of all AUR packages are utter crap (but I won't tell which ;-)
N°1 solution is to just edit the PKGBUILD before building the package and remove the python2 bits, maybe provide a python-giturlparse-p3-only AUR package or whatever.
N°2 solution is to bang the maintainer and that you think this is not an ideal approach and have a fancy and/or productive discussion w/ him.
Blogging about your itches on the forum is going nowhere, so some maintainer will move this TGN and then you'll grunt about being TGN'd…
Offline