On Tue, Sep 30, 2003 at 07:28:37PM -0700, Matt Kraai wrote:
Because it can't use just any partioning program, it uses a
particular one (or, actually, a particular one, two, or three)
depending on the architecture. If we depend on a virtual
partitioning-program package, it could install parted-udeb only
even though that doesn't work on that particular architecture.
Am I missing something on subarchitecture vs. architecture here? Once again:
If parted is not (for our purposes) usable on hppa, we do not build it for
hppa. (That should be quite easy to change.) Likewise, we only build the
other udebs for the platform we intend it to be used on. Thus, there will be
one (and only one) udeb that provides "partitioning-program" (or
"preferred-di-partitioning-program" if you want :-) ) for each architecture,
and anna can easily pick that one.