On Thu, Mar 24, 2016 at 6:50 PM, Adam Borowski <kilob...@angband.pl> wrote:
> Package: wnpp > Severity: wishlist > Owner: Adam Borowski <kilob...@angband.pl> > > * Package name : arch-detect > Upstream Author : me > * URL : https://github.com/kilobyte/arch-detect > * License : MIT > Programming Lang: mostly assembler > Description : detect architectures supported by your machine/kernel > > It seems like the naming would clash with archdetect (from hw-detect, built with some libdebian-installer magic). That package is currently just a udeb, but it *does* make sense as a standard package, there might simply be a need to do some renaming. I'm not saying it's a bad name, just that there already exists an archdetect, and having just a - as a difference may be confusing. It may be worth combining the two "projects" if possible. I know archdetect should work on kfreebsd-*. > This package lets you enumerate architectures that your kernel can run. > The check is for the ability to run machine code and supporting > appropriate > syscall ABI -- you may need to install userland libraries in a chroot, > container or via multiarch to actually execute non-static binaries of such > architectures. > What would the expected output be on a typical amd64 system? Does it differentiate between EFI and non-EFI? / Matt
