Bug#89697: why is this tagged won't fix?

[dannf@dannf.org (dann frazier)]

On Thu, Jun 13, 2002 at 11:38:40AM +0200, Wichert Akkerman wrote:
> Because
> 1) the current tools can not handle it at all
> 2) I'm not convinced it is something you want to do

thanks for your response.
as a data point, here's why i was wanting to use it:
    a package i maintain (systemimager) now supports multiple
  architectures.  systemimager is odd in that it has a set of
  binaries that are not intended to be executed on the machine
  on which they are installed - they are executed on client
  machines, which may be of a different architecture.

  I am planning on having a set of arch-any packages called:
    systemimager-boot-standard-<arch>, where <arch> is the architecture
  of the client machine, and therefore the architecture of the machine
  on which it must be built.  iow, the architecture of the build
  machine directly affects the name of the packages that are generated.

  Being able to have 1 package with a variable name in debian/control
  would prevent me from having a separate package for each arch
  SystemImager supports.

> 3) we can always revisit this discussion later, at this moment I have no
>    intention of fixing it
> 
> Wichert.
> 

-- 

dannf@dannf.org 


-- 
To UNSUBSCRIBE, email to debian-dpkg-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org