Guillem Jover <[EMAIL PROTECTED]> writes:
> Hi,
>
> I've been thinking on implementing this for a long time. As
> Robert has presented an implementation to the Architecture
> handling problem that does not convince me at all, so instead
> of just sitting here and criticize his design I've coded mine.
>
> 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.
> The aliases are of the form:
>
> Alias Example Expansion
>
> <kernel>-any hurd-any hurd-i386
> linux-any i386 powerpc alpha arm ...
% type-handling any linux
alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 s390x sh3 sh3eb sh4
sh4eb sparc sparc64 amd64
> any-<cpu> any-i386 hurd-i386 kfreebsd-i386 i386 ...
% type-handling i386 any
darwin-i386 freebsd-i386 hurd-i386 kfreebsd-i386 knetbsd-i386 i386 netbsd-i386
openbsd-i386
> There are two other cases just for consistency:
>
> linux-<cpu> linux-i386 i386
> any-any any
% type-handling i386 linux
i386
% type-handling any any
alpha arm hppa darwin-i386 freebsd-i386 hurd-i386 kfreebsd-i386 knetbsd-i386
i386 netbsd-i386 openbsd-i386 ia64 m68k mips mipsel darwin-powerpc powerpc s390
s390x sh3 sh3eb sh4 sh4eb sparc sparc64 amd64
I guess that could be improved.
> I've a added as well a new option (-n normalize) to dpkg-architecture
> so Maintainers can use it to get the alias expansions. Try it to see
> the results.
>
> regards,
> guillem
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
