Guillem Jover 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: architecture any on
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
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 messag
On Thu, 2010-06-03 at 13:09:38 -0700, Russ Allbery wrote:
> Guillem Jover writes:
> > On Thu, 2010-06-03 at 09:56:30 -0700, Russ Allbery wrote:
>
> >>
> >>In the main debian/control file in the source
> >> - package, this field may contain the special value
> >> - any, the
Guillem Jover writes:
> On Thu, 2010-06-03 at 09:56:30 -0700, Russ Allbery wrote:
>>
>> In the main debian/control file in the source
>> -package, this field may contain the special value
>> -any, the special value all, or a list of
>> -architectures separ
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 i
Guillem Jover 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 internal representa
"Giacomo A. Catenazzi" 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 os-any and
> + any-cpu. Internally, the package
> T
Russ Allbery wrote:
"Giacomo A. Catenazzi" 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?
"Giacomo A. Catenazzi" 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?
> Personally I woul
On Fri, Sep 18, 2009 at 10:35:03AM +0200, Giacomo A. Catenazzi wrote:
> Manoj Srivastava wrote:
>> +
>> +
>> + A package may specify an architecture wildcard. Architecture
>> + wildcards are in the format os-any and
>> + any-cpu. Internally, the package
>> +
Manoj Srivastava wrote:
+
+
+ A package may specify an architecture wildcard. Architecture
+ wildcards are in the format os-any and
+ any-cpu. Internally, the package
+ system normalizes the GNU triplets and the Debian
+ arches into Debian arch
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
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. T
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 discussion
15 matches
Mail list logo
