Bug#291939: Bug#268377: Bug#291939: Support for arch aliases
On Mon, Jan 24, 2005 at 11:45:24AM +0100, Goswin von Brederlow wrote:
> Guillem Jover <firstname.lastname@example.org> writes:
> > The idea is to introduce architecture aliases, they will only take
> > effect on the source package and will get expanded when building
> > the binary package so there's not need to touch major infrastructure
> > to support this, also they respect current syntax. They can be used
> > on Build-Depends and friends and on Architecture fields on specific
> > packages.
> type-handling already does all you ever want.
No, it does not. And as Robert has explained in another mail it
needs hacks like an autogenerated control file, and use of self
defined "aliases", etc. My patch, what does is integrate that
functionality into the tools that handle debian source packages
so we get that support for free in a clean way. I'll use a more
explicit example this time:
Build-Depends: libasound2-dev [linux-any], libsvga1-dev [linux-any],
The linux-m68k is just for consitency, no need to use this, but it
make it clear that the dependency is not for all m68k based ports
(not that we have any, but who knows :), just for the linux based
On another thread, Goswin von Brederlow wrote:
> Could we automatically define some @linux@ or @any-i386@ variables the
> same way shlidbs or other substitutions work?
That's exactly what my patch tries to do, but extending the
recognised normal arches with some aliases that get expaned and
normalized to normal debian archtitectures, the ones the binary
tools can and know how to handle.