-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parse_packages()
behaviour with empty file.
#107
Comments
It could also be zero lines. |
The warning is not intentional, TBH I am not sure if an edge case should throw a warning. Why is a warning useful for you? |
In my case I was scanning through all the PACKAGES files in a CRAN-like repository, using But seeing as this is a very uncommon use case, it's perhaps not worth the warning. |
OK, let me think about this at the next pkgcache release. I am a bit reluctant to add a warning, because I can imagine that some |
Working with JFROG Artifactory, one can occasionally encounter an empty PACKAGES file. I think it's nice to warn when this happens (which is the current behaviour, see below), although an argument can be made for throwing an error. If it remains a warning, it would be nice to make it more specific.
Created on 2024-03-08 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered: