From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new virtual/pkgconfig to support lighter alternatives
Date: Mon, 30 Apr 2012 17:17:57 -0400 [thread overview]
Message-ID: <201204301717.58217.vapier@gentoo.org> (raw)
In-Reply-To: <4F9ED991.3010002@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1634 bytes --]
On Monday 30 April 2012 14:27:29 Samuli Suominen wrote:
> +1 for creating the virtual and migrating the tree to use
> virtual/pkgconfig. although, on the otherhand, you could just use
> package.provided for thesetype of unsupported experiments (like i'm
> doing with pkgconfig-openbsd)
ok, with no one against the virtual, i'll implement it
> [1] pkgconf is not compatible as per Comment #5 of bug 413849. needs to
> follow same version scheme as f.d.o's pkg-config.
there seems to be miscommunication there. it's compatible.
> [2] pkg-config-lite should be punted from tree as per bug 414101,
> unnecessarily bundling glib code.
not getting punted. what little glib code it bundles (and it really is quite
little) is hand extracted. it doesn't just drop the glib tarball in there.
would be nice if the eglib replacement (that bluez used to use) grew legs ...
then we could even use that.
otherwise, much of the glib funcs are brain dead simple and can be replaced
with #defines. g_free() for example is a waste of space.
> there is no real problem with using
> external glib. not liking it doesn't make it a problem. it's perfectly
> bootstrappable and the bootstrapping is documented (plus ebuilds does
> this for users so it's nothing you should even be thinking about...)
glib-2 is not an acceptable hard requirement. its hard requirement on full
locale/multibyte support is a non-starter.
> [3] pkgconfig-openbsd is incompatible in many ways, for example, doesn't
> pass -pthread/-lpthread properly and breaks on -Wl,--as-needed systems.
i have no interest in that
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-30 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 22:11 [gentoo-dev] new virtual/pkgconfig to support lighter alternatives Mike Frysinger
2012-04-29 22:40 ` Jeff Horelick
2012-04-30 4:08 ` Mike Frysinger
2012-04-30 4:17 ` Jeff Horelick
2012-04-30 5:06 ` Luca Barbato
2012-04-30 6:16 ` Michał Górny
2012-04-30 6:31 ` Jeff Horelick
2012-04-30 16:06 ` Mike Frysinger
2012-04-29 23:29 ` Luca Barbato
2012-04-30 0:19 ` Richard Yao
2012-04-30 18:27 ` Samuli Suominen
2012-04-30 18:40 ` Jeff Horelick
2012-04-30 21:17 ` Mike Frysinger [this message]
2012-04-30 19:07 ` Michał Górny
2012-04-30 19:42 ` Samuli Suominen
2012-04-30 21:12 ` Mike Frysinger
2012-05-02 12:09 ` heroxbd
2012-05-02 16:06 ` Mike Frysinger
2012-05-04 9:30 ` Jeff Horelick
2012-05-04 16:19 ` Mike Frysinger
2012-05-04 9:43 ` Samuli Suominen
2012-05-04 19:34 ` Mike Frysinger
2012-05-05 18:02 ` Jeff Horelick
2012-05-05 18:09 ` Samuli Suominen
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=201204301717.58217.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox