Re: Directory Organization for Sub-Architectures?
> Oh, are there really so few packages? In that case, I think the
> preinst checks are the easiest way. I thought there were many more
> packages affected (like 100).
Currently there are 4 existing packages, and 7 more to come soon on
m68k. I could also imagine that there are several more little
utilities that just aren't packaged yet. Would make a total of 10..20
for m68k. And I've heard that powerpc has the same trouble with fdisk,
due to PowerMac vs. PowerPC, so here subarchs would be useful, too.
Not to forget these Japanese i386 machines... So 100 is maybe a bit
much, but 50 could be reached.
But the problem is a different one: Take as example the
{amiga,atari,mac}-fdisk packages. All are currently base/required (we
haven't made them Essential: yes, see below), but they're really
required only on the appropriate machine type. The same applies to
*-bootstrap and kernel-image-* (which are also different). Now dselect
(or any other package manager) will select all those 3 packages
automatically, but the user only needs one of them. I suppose the #1
FAQ for Debian/68k will be "how can I remove those fdisk packages I
will never need?" :-)
Having subarchs would us enable to create *-fdisk-cross packages with
section/priority otherosfs/extra, removing the problem described
above. (Such -cross packages already exist, but only for other
*architectures*, not *sub*-architectures.) And please remember that
not only the fdisks are affected, but also bootstraps and kernel
images...
Roman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: