Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 21 |
Nodes: | 6 (0 / 6) |
Uptime: | 28:52:54 |
Calls: | 139 |
Files: | 91 |
Messages: | 42,690 |
I'm not opposed to splitting the package per se, but I want to pointI THINK this is currently impossible, or at least I can't figure out a
set of Build-Depends that would achive this result. It maybe would be
enough to add a Multi-Arch tag, but it would be clearer to split the dev
stuff (*.h and *.pc) into a separate package, and that package should be
Multi-Arch:same.
Thinking about this some more, I'm fairly certain that splitting the
package is the correct way to do this because the -dev package shouldn't >require python3 to be installed, which is currently required by numpy. >Installing a foreign-architecture python3 requires qemu, so that's never
what we want.
Furthermore, some packages (like "mrcal", for instance) require numpy at >build-time for two purposes:
- Build-time code generation. This needs numpy:native
- Accessing numpy.pc to build the extension module. this needs
numpy:foreign
So if we really wanted to make this work without splitting the current >python3-numpy package, it would need to be Multi-Arch:same AND be happy >installing only the native python3. This isn't obviously possible, and
even if it were, splitting the package would make this much clearer.
Unless I hear an objection or a better idea here, I'm going to implement >this, and propose a patch in a reply to this bug.