Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] divine: fix divine-config
Date: Fri, 04 Jan 2013 11:29:43 -0300	[thread overview]
Message-ID: <50E6E757.10809@zacarias.com.ar> (raw)
In-Reply-To: <CAHXCMMKhDpanjesHYjMSh-dcAHKt-84B3gEgyzs6UgN_8VRZvQ@mail.gmail.com>

On 01/04/2013 11:17 AM, Samuel Martin wrote:

> We quickly talked about this during the last Buildroot Dev. Days.
> 
> IIRC, Thomas and Peter were not very fond of this kind of solution.
> (guys, feel free to correct me if I speak with my ass ;)).
> 
> btw, afaics:
> - *-config provided by the imagemagick package wrap some calls to pkg-config;
> - many packages in BR install handwritten scripts like this, as well
> as some *.pc files.
> So what about just use pkgconf since it's properly handled in BR?
> (I agree it may mean patching many packages that only search for
> *-config scripts)
> - in this patch serie, only libgcrypt does not provide a *.pc file :-(
> 
> Regards,

I agree *-config files aren't nice, but they are still here and quite used.
When the scenario is a "not very standard" *-config file that can't be
easily fixed, one could just avoid the autopatcher and do it the old
fashion way.
It's a good goal to get rid of them, but realistically it won't happen
anytime soon - you'll need to get *.pc files for *-config packages that
don't provide them, and you'll also need to patch a lot to get them to
use said pc files (with the added dep to host-pkgconf which is now small
given my migration away from pkg-config hehe).
Long story short, they're still here, so why not do it nicely until we
get rid of them all?
Just for fun, try to autoreconfigure PHP and see what happens. It's a
heavy user of *-config scripts :)
Regards.

  reply	other threads:[~2013-01-04 14:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 22:09 [Buildroot] [PATCH] divine: fix divine-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] giblib: fix giblib-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imlib2: fix imlib2-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libgcrypt: fix libgcrypt-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] imagemagick: fix Magick[++|Core|Wand]-config Stefan Fröberg
2013-01-04 21:45   ` Peter Korsgaard
2013-01-03 22:09 ` [Buildroot] [PATCH] neon: fix neon-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] libnspr: fix nspr-config Stefan Fröberg
2013-01-03 22:09 ` [Buildroot] [PATCH] xlib_libXft: fix xft-config Stefan Fröberg
2013-01-04 23:30   ` Peter Korsgaard
2013-01-05 13:33     ` Stefan Fröberg
2013-01-04 11:41 ` [Buildroot] [PATCH] divine: fix divine-config Gustavo Zacarias
2013-01-04 14:17   ` Samuel Martin
2013-01-04 14:29     ` Gustavo Zacarias [this message]
2013-01-04 14:56       ` Stefan Fröberg
2013-01-04 15:00         ` Gustavo Zacarias
2013-01-06  5:41         ` Baruch Siach
2013-01-06  8:27           ` Samuel Martin
2013-01-06  8:34             ` Baruch Siach
2013-01-06 12:39               ` Thomas Petazzoni
2013-01-06 14:15           ` Stefan Fröberg
2013-01-06 18:12           ` Stefan Fröberg
2013-01-07 22:17             ` Arnout Vandecappelle
2013-01-07 22:35               ` Stefan Fröberg
2013-01-08  7:48                 ` Arnout Vandecappelle
2013-01-08  8:10                   ` Thomas Petazzoni
2013-01-08  8:24                     ` Arnout Vandecappelle
2013-01-04 16:29     ` Thomas Petazzoni
2013-01-04 16:31   ` Thomas Petazzoni
2013-01-04 17:10     ` Gustavo Zacarias
2013-01-04 17:13       ` Stefan Fröberg
2013-01-04 21:49 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50E6E757.10809@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox