![]() Like I already said, change the name and make it provide the stuff you want. I'll say it again, this weird but correct behaviour is because you gave your package the same name as one already in the aur. Yay can only get packages by name, split or not. Points 1 and 2 should be impossible because the rpc does not do split packages. Why only installed dependencies? What happens if a package updates and gets a new dependency that the user does not have installed? Should Yay ignore that? What happens if you -S a package and don't have all the deps? Nor does it mean that Yay is going to install it, simply that Yay looked it up and thought to point it out. It does not mean it's installed and needs an update, it means the PKGBUILD is out of date and the maintainer needs to update it. That warning comes from when Yay looks up a package on the AUR and the package is out of date: Yes, it shouldn't print a warning because perl-hash-multivalue isn't installed on my system (never would have been, if I didn't install it for bug troubleshooting), isn't required by any package on my system, isn't in an any AUR PKGBUILD depends array of any package installed on my system. The bug is that it prints a warning when it shouldn't? Optimally we would want yay to only look at currently installed eiskaltdcpp-qt-git depends.Īnyway, I think it's unrelated to the bug I reported.
0 Comments
Leave a Reply. |