Hi Frank, On Sun, Jun 10, 2012 at 12:07:34PM +0200, Frank Lichtenheld wrote: > You mean "foreign" here, like you wrote in the subject, right?
Thanks for spotting. Foreign of course. > I don't know if "foreign" is really correct, though. It would be > correct certainly if we only had Linux kernels. But the Linux version > will not work on kFreeBSD and vice versa, because some of the > kernel interfaces differ. Should I still add this? The multiarch classification is about the interface a package provides, not about the interface a package expects to use. So foreign is correct here, because the only way for other packages to interact with eject is by using the command line. For instance you should be able to install iproute:amd64 which is ma:foreign on kfreebsd-amd64 even though it will not work at all. Expressing that eject actually relies on a specific kernel should be done in a dependency, but that seems a bit harder (if possible at all). Even now you should be able to install eject:amd64 on kfreebsd-amd64 just by mixing those two architectures. Thank you for your attention to the detail Helmut -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
