+++ Raphael Hertzog [2011-03-24 14:31 +0100]:
> Hi,
> 
> On Thu, 24 Mar 2011, Wookey wrote:
> > It is probably not hard to enforce this at a slightly higher level.
> > Indeed, it may make sense to just parse any string after the :, then
> > have higher-level checks for valid values. The multiarch spec
> > explicitly says to reject anything other than :any (in depends) for now, 
> > but in the
> > future this syntax will be used to allow cross-architecture
> > dependencies so any valid architecture name should be accepted.
> 
> I don't think I want to enforce it at a higher level. deps_parse() should
> be modified to accept a new parameter so that we know what to accept
> or not. And we enforce it either within deps_parse or within
> Dpkg::Deps::Simple.

OK, sounds sensible. I've never looked at this code before yesterday so
defer entirely on what the best way to treat this stuff is :-)

> > This patch is intended to be a simple implementation that allows
> > packages with this info to be used with the build-tools, and
> > ultimately uploaded to the archive (once a few more dependency-parsing
> > packages have been fixed) - nothing more. 
> 
> We already have a patch very similar to yours in the multiarch branch. Can
> you develop your patch so that it applies on top of the existing one?
> 
> http://git.debian.org/?p=users/hertzog/dpkg.git;a=shortlog;h=refs/heads/pu/multiarch/full
> http://git.debian.org/?p=users/hertzog/dpkg.git;a=commitdiff;h=23efdcadd7c3fea81079e65ff3a89de37feb0c58

OK. I realised after posting this that there was already some very
similar code in dpkg 1.16.0 in natty. So I did a patch against that
here: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/741433
which is probably very close to what you are asking for. I'll check
aginst git though.



Wookey
-- 
Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/




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

Reply via email to