Hi @sage-etcher thanks for the fix you have provided with #54!
Unfortunately (or fortunately? :P) this exposes a follow up bug in version resolution in case of PIP!
For example, I've added a dependency PIP3:meson to the Dependency file of recipe Tree 2.1.3.
Upon running Compile Tree or simply: CheckDependencies Tree it will prompt us to install meson 0.29.0.dev1 - which is the oldest one in the repo: https://pypi.org/project/meson/#history. If we specify > 0.29.0 it picks the next lowest version.
I have tested it with other PIP packages with the same results....
Interestingly in the case of LuaRocks (e.g. LuaSocket) the latest dependency is correctly picked. Also a dependency definition like LuaRocks:LuaSocket < 3.1.0 correctly picks 3.0.0.
Others like CPAN seems to work resonably as well (it at least picks the latest version), although I could not test most of them like Cabal, CTAN, RubyGems, etc since they are not even present on my machine or a default gobo installation at this time.
Therefore it could be that the bug lays within PIP sepecific code: https://github.com/gobolinux/Scripts/blob/master/bin/Alien-PIP, or maybe it lays somewhere else.
I do not consider the other package managers integrations that crucial right now, but PIP is an important one that needs to work correctly for our packaging purposes.
Hi @sage-etcher thanks for the fix you have provided with #54!
Unfortunately (or fortunately? :P) this exposes a follow up bug in version resolution in case of
PIP!For example, I've added a dependency
PIP3:mesonto theDependencyfile of recipeTree 2.1.3.Upon running
Compile Treeor simply:CheckDependencies Treeit will prompt us to installmeson 0.29.0.dev1- which is the oldest one in the repo: https://pypi.org/project/meson/#history. If we specify> 0.29.0it picks the next lowest version.I have tested it with other PIP packages with the same results....
Interestingly in the case of
LuaRocks(e.g.LuaSocket) the latest dependency is correctly picked. Also a dependency definition likeLuaRocks:LuaSocket < 3.1.0correctly picks3.0.0.Others like
CPANseems to work resonably as well (it at least picks the latest version), although I could not test most of them likeCabal,CTAN,RubyGems, etc since they are not even present on my machine or a default gobo installation at this time.Therefore it could be that the bug lays within PIP sepecific code: https://github.com/gobolinux/Scripts/blob/master/bin/Alien-PIP, or maybe it lays somewhere else.
I do not consider the other package managers integrations that crucial right now, but PIP is an important one that needs to work correctly for our packaging purposes.