On Fri, Apr 26, 2013 at 1:31 PM, Pino Toscano wrote:
> Just one niptick more: you can replace «kfreebsd-amd64 kfreebsd-i386»
> with just «kfreebsd-any» in both the libkvm-dev build dependency and in
> the Architecture control field. There's nothing potentially specific to
> amd64 or i386, so (once
Alle venerdì 26 aprile 2013, Kartik Mistry ha scritto:
> On Fri, Apr 26, 2013 at 1:13 PM, Pino Toscano wrote:
> > Thanks, but why leaving it commented and removing the kfreebsd
> > build? After all, xosview on kfreebsd has not been compiled
> > before, so having it fail is not a regression wrt pre
On Fri, Apr 26, 2013 at 1:13 PM, Pino Toscano wrote:
> Thanks, but why leaving it commented and removing the kfreebsd build?
> After all, xosview on kfreebsd has not been compiled before, so having
> it fail is not a regression wrt previous versions (thus it won't stop
> xosview migrating to testi
Alle venerdì 26 aprile 2013, Kartik Mistry ha scritto:
> On Fri, Apr 26, 2013 at 2:05 AM, Pino Toscano wrote:
> > the changes in the experimental version still make xosview compiled
> > as "linux" even in non-Linux OSes, and never uses the right
> > platform string on kFreeBSD.
> > The attached pa
On Fri, Apr 26, 2013 at 2:05 AM, Pino Toscano wrote:
> the changes in the experimental version still make xosview compiled as
> "linux" even in non-Linux OSes, and never uses the right platform
> string on kFreeBSD.
> The attached patch factorizes the detection of the platform string
> to use when
Source: xosview
Version: 1.14-1
Severity: wishlist
Tags: patch
Hi,
the changes in the experimental version still make xosview compiled as
"linux" even in non-Linux OSes, and never uses the right platform
string on kFreeBSD.
The attached patch factorizes the detection of the platform string
to use
6 matches
Mail list logo
