[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: is dpkg new architecture specifications going to be fixed and documented?



Hi,

> > On Mon, May 15, 2006 at 01:46:49PM +0900, Junichi Uekawa wrote:
> > > I was discussing with Christian Perrier at dinner and he mentioned
> > > that the new-style architecture specifications (Build-Depends: XXX
> > > [linux-any] etc.) may have been reverted.  I'm not quite sure about
> > > that since the documentation and changelogs are quite scarse about
> > > dpkg-dev stuff.
> > > 
> > > Am I okay in going ahead with committing this change to pbuilder ?
> 
> Please use instead dpkg-architecture -e or -i options (documented in
> the man page), so that we have this code centralized there, and can
> extend or fix it in just one place.

The descriptions for the following are very vague.
I suggest you reword them to:

.BI "-e" "debian-architecture"

Check for equality of architecture. By default the 
.I "debian-architecture"
is compared against the current Debian Architecture, being the host.
.B "-e"
will not expand architecture aliases.

Command exits with exit code of 0 if matched, 1 if not matched.

.BI "-i" "architecture-alias"

.B "-i"
will expand 
.I "architecture-alias"
as an Architecture Alias, and is compared against the current Debian Architecture.

Command exits with exit code of 0 if matched, 1 if not matched.



Some examples would be nice too.

> You'll have to depend on a new enough version of dpkg (1.13.17) or
> conditionally use the feature if that dpkg version is present.
> 
> About the bug report, if you find the documentation lacking in
> dpkg-architecture's man page I can extend it, otherwise please
> close it.

please close bug #370830 with an updated manpage.



Build-Depends is usually a space-delimited list; I assume
dpkg-architecture does not take a list of architectures; which means
it needs to be forked every time an architecture string exists.

I have another concern. dpkg-architecture is a pretty expensive
program to fork/exec, and I don't think it's realistic to expect
everyone to be using this code.



regards,
	junichi
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project



Reply to: