On Sat, Mar 08, 2003 at 05:37:58PM +0100, Raphael Hertzog wrote:
> First, knowing the architecture field doesn't let you know if the
> package is built for a given architecture but only if it should be built
> for a given architecture.
That's what I meant, sorry :)
> Third, I fail to see how displaying this info will make it easier for
> maintainer to support archs they don't have access to.
When I create a package I have to fill/update the build-depends fields, and
what to put in it sometimes depends on the arch. Currently "tulip" does not
autobuild on most archs just because I have added a single package to the
build-dep list - while investigating, the buildd error first made me thought
this may have been a non-"arch:any" package.
> Second, most packages have "any" or "all", so the information is rather
> not very interesting.
[...]
> I'm tempted however to display the global "architecture" field of the
> source if it is different from "any" or "all" ... that way you'll notice
> that efibootmgr is ia64-specific and the like.
This sounds like a good solution.
Regards,
--
Yann Dirson <[EMAIL PROTECTED]> | Why make M$-Bill richer & richer ?
Debian-related: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
Pro: <[EMAIL PROTECTED]> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>
