(I'm the maintainer of the Debian package of scsh.)
I was looking into what it would take to make the Debian package of
scsh play nice with the packaging proposal and I noticed that right
now (mostly) everything is stuck in /usr/lib/scsh. Most of these files
(*.scm) look architecture-independent at first glance to me; in this
case, they should be in /usr/share/scsh/.
But for all I know, they may contain architecture-dependent define'd
constants, and thus be really architecture-dependent, so I wanted to
check with you first. Could you please tell me which files are really
system dependent? Thanks.
Please note that architecture-dependence might come from CPU
architecture dependence (IA32 vs Sparc vs PPC vs ...), but also from
dependence on the kernel, the libc or the combination thereof. Indeed,
Debian is preparing ports using the (Free|Net|Open)BSD kernel with the
GNU libc or with the (Free|Net|Open)BSD libc and the GNU Hurd. Thus,
if a file depends on the kernel used (e.g. contains the hardcoding of
syscall numbers, errno numbers, signal numbers, a "Unix flavour
quircks abstraction layer", ...), they must be considered
"architecture dependent" for Debian purposes.
Best Regards and thank you for your help,