Closed MatthewBlanchard closed 13 years ago
Fixed it to set the not found package to 0, no package should ever be 0 I'm assuming.
'Don't do anything on package not found' is a feature, not a bug. It doesn't need fixing.
Oh alright, I just thought it was weird that it did this even if they weren't dependent on each other, or related.
Example:
:: blah package not found, searching for group... :: blah group not found, searching AUR... error: 'blah': not found in sync db, skipping :: lanes package not found, searching for group... :: lanes group not found, searching AUR...
==> Installing the following packages from AUR Targets (1): lanes
==> Proceed with installation? [Y/n]
Instead of:
:: blah package not found, searching for group... :: blah group not found, searching AUR... error: 'blah': not found in sync db
I did this kind of hackily. (although the code is really all over the place, so it was hard for me to figure most of it out)