Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Russ Allbery
Guillem Jover guil...@debian.org writes: On Thu, 2010-06-03 at 00:06:39 +0200, Guillem Jover wrote: From a comment somewhere else I think you understand it now, but anyway just to make sure, it allows adding new architectures in dpkg w/o needing to recreate the source package from its

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Guillem Jover
Hi! On Thu, 2010-06-03 at 09:56:30 -0700, Russ Allbery wrote: Okay, here's another try at this patch that removes some extraneous information that it sounds like we shouldn't get into, from this message and your other message, and tries to simplify the wording to address the issue raised in

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Russ Allbery
Guillem Jover guil...@debian.org writes: On Thu, 2010-06-03 at 09:56:30 -0700, Russ Allbery wrote: p In the main filedebian/control/file file in the source -package, this field may contain the special value -ttany/tt, the special value ttall/tt, or a list of

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Guillem Jover
On Thu, 2010-06-03 at 13:09:38 -0700, Russ Allbery wrote: Guillem Jover guil...@debian.org writes: On Thu, 2010-06-03 at 09:56:30 -0700, Russ Allbery wrote: p In the main filedebian/control/file file in the source - package, this field may contain the special value -

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Andrew McMillan
On Thu, 2010-06-03 at 22:01 +0200, Guillem Jover wrote: Hi! On Thu, 2010-06-03 at 09:56:30 -0700, Russ Allbery wrote: Okay, here's another try at this patch that removes some extraneous information that it sounds like we shouldn't get into, from this message and your other message, and

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Steve Langasek
On Thu, Jun 03, 2010 at 09:56:30AM -0700, Russ Allbery wrote: Okay, here's another try at this patch that removes some extraneous information that it sounds like we shouldn't get into, from this message and your other message, and tries to simplify the wording to address the issue raised in

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2010-06-03 Thread Russ Allbery
Guillem Jover guil...@debian.org writes: Yes, dpkg-source will reject such package. The check has always been there, it just never got relaxed when introducing the generic wildcard support. This is the actual error when using as value for example “any linux-any”: dpkg-source: error:

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-21 Thread Giacomo A. Catenazzi
Russ Allbery wrote: Giacomo A. Catenazzi c...@debian.org writes: Do we really need to use the triplets? Do you see some possible cases where we must really specify the first part? Isn't someone working on a klibc port? That would require using the triplet. Does the new dpkg support also

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-21 Thread Russ Allbery
Giacomo A. Catenazzi c...@debian.org writes: ok. fair enough. BUT: the original proposal and this proposal contain only the duet: + A package may specify an architecture wildcard. Architecture + wildcards are in the format ttvaros/var/tt-any and +

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-19 Thread Bill Allombert
On Fri, Sep 18, 2009 at 10:35:03AM +0200, Giacomo A. Catenazzi wrote: Manoj Srivastava wrote: + +p + A package may specify an architecture wildcard. Architecture + wildcards are in the format ttvaros/var/tt-any and + any-ttvarcpu/var/tt. footnoteInternally,

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-19 Thread Russ Allbery
Giacomo A. Catenazzi c...@debian.org writes: Do we really need to use the triplets? Do you see some possible cases where we must really specify the first part? Isn't someone working on a klibc port? That would require using the triplet. Does the new dpkg support also the triplets?

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-18 Thread Giacomo A. Catenazzi
Manoj Srivastava wrote: + +p + A package may specify an architecture wildcard. Architecture + wildcards are in the format ttvaros/var/tt-any and + any-ttvarcpu/var/tt. footnoteInternally, the package + system normalizes the GNU triplets and the Debian

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-11 Thread Peter Pentchev
On Thu, Sep 10, 2009 at 04:28:55PM -0500, Manoj Srivastava wrote: Support for architecture wildcards has been added to dpkg-1.13.13. This patch, based on a proposal from Andres Mejia, provides policy on how architecture wildcards should be used for other tools such as sbuild and pbuilder. This

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-11 Thread Manoj Srivastava
On Fri, Sep 11 2009, Peter Pentchev wrote: On Thu, Sep 10, 2009 at 04:28:55PM -0500, Manoj Srivastava wrote: Support for architecture wildcards has been added to dpkg-1.13.13. This patch, based on a proposal from Andres Mejia, provides policy on how architecture wildcards should be used for

Bug#530687: [PATCH] bug530687-srivasta: Support for architecture wildcards

2009-09-10 Thread Manoj Srivastava
Support for architecture wildcards has been added to dpkg-1.13.13. This patch, based on a proposal from Andres Mejia, provides policy on how architecture wildcards should be used for other tools such as sbuild and pbuilder. This patch has tracked and incorporated suggestions embedded the