bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] teach ncurses-config about sysroot


From: Mike Frysinger
Subject: Re: [PATCH] teach ncurses-config about sysroot
Date: Fri, 27 Aug 2010 17:10:36 -0400
User-agent: KMail/1.13.1 (Linux/2.6.35.2; KDE/4.4.5; x86_64; ; )

On Thursday, August 26, 2010 18:57:20 Enrico Weigelt wrote:
> * Mike Frysinger wrote:
> > try reading the whole thread.  adding $SYSROOT to ncurses-config is
> > *exactly* what you're indicating here is a bad idea -- "tweaking each
> > single package".
> 
> No. In this case, it's a generic solution, which is similar to
> pkg-config's sysroot handling (just another name for the variable,
> which actually is more obvious and almost de-facto standard).

it's only generic when a standard exists and people are adopting it.  no one 
has adopted this and it doesnt look like that is going to change.

Thomas already pointed out that ncurses has started shipping a .pc file so 
there's no reason to use the config script anymore.

> And in this case, This patch only has to applied once to the package
> (and hopefully will be taken into next upstream release) - there's no
> need to tweak it per-target and for each new version again.

a good example of why anyone using stuff from oss-qm needs to be caveat 
emptor.  this patch has already been rejected (and for good reason).  this 
oss-qm tree is turning out to be more of a fork with changes that dont belong 
in distros.

> > instead, the sane solution is what we implemented in Gentoo long
> > ago -- a single tool that automatically wraps all *-config scripts
> > and fixes their output.
> 
> Well, that's quite what I was doing w/ pkg-config, before it supported
> sysroot on it's own. (now it's not needed anymore). But doing it
> for all *-config scripts can turn out to be a bit tricky, not just
> because their semantics are not standardized.

funny, we havent had a problem
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]