Bug#1005959: mig-for-host:amd64 should not exist

[Helmut Grohne <helmut@subdivi.de>]

Control: tags -1 + moreinfo

Hi Guillem,

On Fri, Feb 18, 2022 at 12:45:57PM +0100, Guillem Jover wrote:
> Just to spell out, what might perhaps be obvious here, but I think
> they key is that MIG is "kernel independent", so it provides an
> interface which is none-<cpu> which means it can be used on any-<cpu>
> to target hurd-<any>. Perhaps this should be mentioned in the packages
> description, because otherwise I agree it seems a bit confusing?

Thank you. In that case, I think it shouldn't be mig-x86-64-linux-gnu
nor mig-x86-64-gnu nor mig-x86-64-kfreebsd-gnu, but simply mig-x86-64 as
that's what it is specific to.

That makes a few downstream-implications a little more difficult though.
The binary would likely have to be called x86_64-mig instead of
x86_64-gnu-mig. mig-for-host can likely stay as it is.

I suppose such renaming would break downstreams such as hurd as they
don't expect such changed names.

At this point I'm unsure whether such a renaming effort would be a
useful thing to spend time on. However improving the description would
be useful.

Helmut