don't require a homepage

[hellow554]

this is not necessary, neither for cargo nor for bitbake and for our internal projects we typically don't set it, so let's skip it plz :)

[kraj]

I think asking for homepage is a good practice. You can keep it empty or undisclosed by saying something there.

[hellow554]

you may be right. It's just a thing I always trip over ^^
Because carg-new doesn't fill in neither the repository nor the homepage I have to add it manually.
And just adding an empty string somehow misses the purpose of the field at all, doesn't it?

So as said, for our internal projects, we never add the homepage field, because we know who we are (:
If you still think it's not worth merging, that's fine for me.

[jo-so]

I think asking for homepage is a good practice. You can keep it empty or undisclosed by saying something there.

I think cargo-bitbake should not add new policies, but be a helper tool and do (map) what's possible/available.

I use cargo-bitbake as a scaffolder and change the recipes according to our policy (ordering of entries in the recipe). But this check for a homepage blocks it all the time.

[paolobarbolini]

I use cargo-bitbake as a scaffolder and change the recipes according to our policy (ordering of entries in the recipe). But this check for a homepage blocks it all the time.

Have you tried cargo-update-recipe-crates (see #83)?