Pkg3 plan and status

Point taken, but I still feel like there is a loss of some form of valuable human readability as opposed to having the REQUIRE file. For example, if I look at a repo on github, I can no longer easily get a good idea of what the requirements are without REQUIRE. Maybe I’m making too much of this, or perhaps I’m just too used to the old way of doing things, but I feel there is some (perhaps small) value in being able to look at a repo and say “Oh, I have to have Compat \ge v"0.66.0”. Unless I’m missing something, you now have to have the package actually installed to infer this simple information. (Granted, there may be packages where the version constraints are much more complicated.)

Great!

1 Like