All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: QA issues with pkgconfig files
Date: Thu, 22 Feb 2007 09:43:53 +0200	[thread overview]
Message-ID: <455328392.20070222094353@gmail.com> (raw)
In-Reply-To: <45DCCAEB.9010603@dominion.kabel.utwente.nl>

Hello Koen,

Thursday, February 22, 2007, 12:42:51 AM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Koen Kooi schreef:

>> Possible solutions:
>> 
>> 1) set PKG_CONFIG_PATH to ${STAGING_LIBDIR}/pkgconfig
>>    +easy fix
>>    -requires to re-run do_pupulate_staging for all packages
>> 2) symlink one dir to the other
>>    +fixes hardcoded paths
>>    -requires manual intervention to fixup files present and/or complete rebuild
>> 3) have pkgconfig.bbclass delete one dir each run
>>    -requires every packages that has .pc files to inherit pkgconfig
>>    -ugly
>>    -error-prone
>> 
>> Do you have any other solutions, and if not, which solution do you prefer?

> 4) have pkgconfig.bbclass sed _every_ .pc file in staging each run.

  Why staging? Shouldn't we add sanitize_XXX(filename) where XXX is
any type of file insane.bbclass checks for, and call it around
do_install? Plus, add sanitize_XXX_recursive() for lazy folks, who
will search for broken stuff in install dir itself - just like insane
currently does, except it will fix it on spot ;-)

> regards,


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2007-02-22  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 22:27 QA issues with pkgconfig files Koen Kooi
2007-02-21 22:42 ` Koen Kooi
2007-02-22  7:43   ` Paul Sokolovsky [this message]
2007-02-22  7:47     ` Koen Kooi
2007-02-22  8:41 ` Koen Kooi
2007-02-22 11:24 ` Koen Kooi
2007-02-22 15:13   ` Koen Kooi
2007-02-22 15:37     ` Holger Freyther
  -- strict thread matches above, loose matches on Subject: below --
2007-02-22 17:06 Mark Gollahon

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=455328392.20070222094353@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.