fix build for latest zig

[vrischmann]

Hello,

There were breaking changes in build.zig.zon with zig master a couple of days:

• the name must be a enum literal. Since zig-args is an invalid enum literal, I changed it to name as recommended in the documentation.
• the fingerprint is a new mandatory field, zig build generates one if it's not present in the file.

Changing the name is obviously a breaking change, users will have to change their build.zig file to use args instead of zig-args; I can change the name to whatever you want if you decide to go ahead with this PR.

[bobf]

@vrischmann Sorry, I made a fork so I could use as a temporary dependency in my project and then made the PR without checking here first.

In my PR I use the name zig_args instead of args - I prefer yours but I guess @ikskuh can choose.

[ikskuh]

Thanks!

Changing the name is obviously a breaking change, users will have to change their build.zig file to use args instead of zig-args; I can change the name to whatever you want if you decide to go ahead with this PR.

No, they don't. The .name field isn't relevant for consuming the package. You can name it in the build.zig.zon however you want, so you only have to update the hash

[vrischmann]

Thanks!

Changing the name is obviously a breaking change, users will have to change their build.zig file to use args instead of zig-args; I can change the name to whatever you want if you decide to go ahead with this PR.

No, they don't. The .name field isn't relevant for consuming the package. You can name it in the build.zig.zon however you want, so you only have to update the hash

You're right, I wasn't clear enough.
What I meant was that if now I rerun "zig fetch" for zig-args the name saved in build.zig.zon will change, and users will have to change their build.zig to use the new name.
But yeah it's not a big deal.