On 09.05.2016 16:37, Jakub Wilk wrote:
* Helmut Grohne , 2016-05-09, 06:47:
The first misconception I see in this thread is that somehow pkg-config is
good and foo-config is bad. It's not as simple as that. Have a look at
libpython3-dev. It ships e.g. x86_64-linux-gnu-python3-config.
This is a
* Helmut Grohne , 2016-05-09, 06:47:
The first misconception I see in this thread is that somehow pkg-config
is good and foo-config is bad. It's not as simple as that. Have a look
at libpython3-dev. It ships e.g. x86_64-linux-gnu-python3-config.
This is an unfortunate example, because Python u
On Mon, 09 May 2016 at 06:47:38 +0200, Helmut Grohne wrote:
> In order for pkg-config to be "better" than your foo-config script, you
> need to tell it about the current host architecture by prefixing it with
> the triplet. Instead of calling pkg-config, you should be calling
> $DEB_HOST_GNU_TYPE-p
On Wed, Feb 10, 2016 at 11:03:04AM +0100, Bastien ROUCARIES wrote:
> On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry
> > In particular, for any non-standard variables, you can read them, by eg:
> >
> > f90_compiler=$(pkg-config mypkg --variable=f90_compiler)
> >
> > Its probably a good idea to
On Fri, Feb 12, 2016 at 8:10 PM, Bastien Roucaries wrote:
> i will open a wiki page including this thread comments
No need to duplicate the official documentation:
https://sources.debian.net/doc/url/
Also no need to CC me.
--
bye,
pabs
https://wiki.debian.org/PaulWise
* Johannes Schauer , 2016-02-12, 13:41:
dpkg-buildpackage: warning: debian/changelog(l1): version '0:jessie' is
invalid: version number does not start with digit
LINE: name (0:jessie) unstable; urgency=medium
According to the following regex over my Sources there seems to be no
source pack
Hi,
Quoting Paul Wise (2016-02-12 02:02:53)
> On Wed, Feb 10, 2016 at 9:09 PM, Johannes Schauer wrote:
> > A bit OT: the old-style-config-script lintian description links to a 404
> > page
> > on sources.debian.net. Maybe this link should be updated? Is there a way to
> > create a link to a file
Hi,
Quoting Bastien Roucaries (2016-02-12 10:10:10)
> Le 12 février 2016 02:02:53 GMT+01:00, Paul Wise a écrit :
> >On Wed, Feb 10, 2016 at 9:09 PM, Johannes Schauer wrote:
> >
> >> A bit OT: the old-style-config-script lintian description links to a
> >404 page
> >> on sources.debian.net. Maybe
Le 12 février 2016 02:02:53 GMT+01:00, Paul Wise a écrit :
>On Wed, Feb 10, 2016 at 9:09 PM, Johannes Schauer wrote:
>
>> A bit OT: the old-style-config-script lintian description links to a
>404 page
>> on sources.debian.net. Maybe this link should be updated? Is there a
>way to
>> create a lin
At Fri, 12 Feb 2016 01:12:43 +0100,
Jakub Wilk wrote:
> I don't know much about this package, but codesearch.d.n tells me that
> all users of chasen-config call it with the --mkchadic option, which
> causes the script to print /usr/lib//chasen/, which is a
> directory shipped by chasen-config. So i
On Fri, Feb 12, 2016 at 10:20 AM, NOKUBI Takatsugu wrote:
> I am also a member of the upstream, but the software is now under
> maintainance phase, so it is hard to accept using pkg-config insead of
> the current script.
> I consider to use pkg-config on debian specific patch in the future.
There
On Wed, Feb 10, 2016 at 9:09 PM, Johannes Schauer wrote:
> A bit OT: the old-style-config-script lintian description links to a 404 page
> on sources.debian.net. Maybe this link should be updated? Is there a way to
> create a link to a file on sources.debian.net where, if the version doesn't
> exi
* NOKUBI Takatsugu , 2016-02-12, 08:27:
Jakub Wilk wrote:
Are you trying to move the script to libchasen-dev? Why? There are
Debian maintainer scripts that use chasen-config. Are they going to
depend on the -dev package?
Yes, now I will move the script into libchasen-dev because it seems
mak
At Wed, 10 Feb 2016 13:17:50 +0100,
Jakub Wilk wrote:
> Are you trying to move the script to libchasen-dev? Why? There are
> Debian maintainer scripts that use chasen-config. Are they going to
> depend on the -dev package?
Yes, now I will move the script into libchasen-dev because it seems
make se
Thank you your good answer.
At Wed, 10 Feb 2016 08:34:10 +0100,
Vincent Danjean wrote:
> I do not think there is a generic answer. But, if your script is
> simple, perhaps just replacing hardcoded directory names by the output
> of "dpkg -qDEB_HOST_MULTIARCH" will be enough.
I think "dpkg-archi
Hi,
Quoting Jakub Wilk (2016-02-11 12:44:34)
> * Johannes Schauer , 2016-02-10, 11:09:
> >The old-style-config-script tag which src:chasen suffers from as well and
> >which was also linked to by Bastien contains more valuable information. The
> >important message is: please use pkg-config and not
* Johannes Schauer , 2016-02-10, 11:09:
I am a maintainer of chasen package. It contains chasen-config, it
work as pkg-config like but it's a single script.
Latest lintain reports:
E: libchasen-dev: old-style-config-script-multiarch-path usr/bin/chasen-config
full text contains architecture sp
* NOKUBI Takatsugu , 2016-02-10, 16:12:
I am a maintainer of chasen package. It contains chasen-config, it work
as pkg-config like but it's a single script.
Latest lintain reports:
E: libchasen-dev: old-style-config-script-multiarch-path usr/bin/chasen-config
full text contains architecture sp
On Wed, 10 Feb 2016 at 11:03:04 +0100, Bastien ROUCARIES wrote:
> On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry
> wrote:
> > I've solved this problem by:
> > (1) creating a pkg-config script, adding it as multiarch.
> > (2) editing the config script to use the pkg-config script.
>
> (2) wr
On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi ,
>
> I've solved this problem by:
> (1) creating a pkg-config script, adding it as multiarch.
> (2) editing the config script to use the pkg-config script.
>
> In particular, f
Hi Nokubi,
Quoting Bastien ROUCARIES (2016-02-10 10:29:46)
> On Wed, Feb 10, 2016 at 8:12 AM, NOKUBI Takatsugu wrote:
> > I am a maintainer of chasen package. It contains chasen-config, it
> > work as pkg-config like but it's a single script.
> >
> > Latest lintain reports:
> > E: libchasen-dev:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi ,
I've solved this problem by:
(1) creating a pkg-config script, adding it as multiarch.
(2) editing the config script to use the pkg-config script.
In particular, for any non-standard variables, you can read them, by eg:
f90_compiler=$(pkg-co
On Wed, Feb 10, 2016 at 8:12 AM, NOKUBI Takatsugu wrote:
> I am a maintainer of chasen package. It contains chasen-config, it
> work as pkg-config like but it's a single script.
>
> Latest lintain reports:
> E: libchasen-dev: old-style-config-script-multiarch-path
> usr/bin/chasen-config full tex
Le 10/02/2016 08:12, NOKUBI Takatsugu a écrit :
> I am a maintainer of chasen package. It contains chasen-config, it
> work as pkg-config like but it's a single script.
>
> Latest lintain reports:
> E: libchasen-dev: old-style-config-script-multiarch-path
> usr/bin/chasen-config full text contain
I am a maintainer of chasen package. It contains chasen-config, it
work as pkg-config like but it's a single script.
Latest lintain reports:
E: libchasen-dev: old-style-config-script-multiarch-path usr/bin/chasen-config
full text contains architecture specific dir x86_64-linux-gnu
But I want to
25 matches
Mail list logo