Hi,

I am wondering whether we should either allow multiple Homepage fields
in debian/control or have this as a multivalue, allowing mor than one
homepage to be listed.

I have a package that is on github and has a homepage, with the server
having the homepage being kind of broken so that it doesn't deliver the
page for all clients. The github page doesn't refer to the real
homepage.

I am therefore tempted to ignore the "real" homepage and set the
Homepage field to the github page here.

Are there tools in Debian other than the Tracker that make use of the
Homepage field? The Tracker could generate one link per value, probably
a three-line change.

Am I talking to the right package to suggest this change?

Greetings
Marc

I need to note that this is usually the correct way, because it's often
hard (sometimes impossible) to get the upstream source from the "real"
homepage, especially when one wants a VCS and not tarballs. It's safe to
assume, on the other hand, that a VCS has a prominent link to a "real"
homepage if that exists and is useful.

OTOH we have additional metadata, e.g. debian/upstream/metadata, and it's
possible that it would be enough for you, but I don't think e.g. tracker
shows it.

We have debian/watch to look for upstream source.

Do we have that documented beyond DEP-12?

Greetings
Marc

Hello,

We can certainly discuss it here but generally Policy would change only
after parsers were updated for something like this.

This is probably for the best. What is upstream saying about this ?

I am afraid having two Homepage: without further semantic would be
confusing for little benefit.

Homepage[kindabroken]: https://www
Homepage[github]: https://github

Cheers,

DEP-12 doesn't allow a Homepage field.

Greetings
Marc