From: Paul Sokolovsky <pmiscml@gmail.com>
To: Graeme Gregory <dp@xora.org.uk>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev packages/glib-2.0/glib.inc : remove bogus ${PN}-dev from packages.
Date: Tue, 10 Jul 2007 12:54:40 +0300 [thread overview]
Message-ID: <986250811.20070710125440@gmail.com> (raw)
In-Reply-To: <E1I8BNL-0002lu-BC@linuxtogo.org>
Hello xora,
Tuesday, July 10, 2007, 11:47:15 AM, you wrote:
> packages/glib-2.0/glib.inc : remove bogus ${PN}-dev from packages.
> Author: xora@openembedded.org
> Branch: org.openembedded.dev
> Revision: 2f67b52cb2be4988db873678ab4f354aea217a90
[]
> ============================================================
> --- packages/glib-2.0/glib.inc
> 09c2d1615f7c249f8ab1c68778bafbc98293ff6b
> +++ packages/glib-2.0/glib.inc
> 3b5260371e84b9c12db9a8cdc8c5809bab8d2ec5
> @@ -8,7 +8,7 @@ DEPENDS += "virtual/libiconv virtual/lib
> PRIORITY = "optional"
> DEPENDS += "glib-2.0-native gtk-doc"
> DEPENDS += "virtual/libiconv virtual/libintl"
> -PACKAGES =+ "${PN}-dev glib-2.0-utils "
> +PACKAGES =+ " glib-2.0-utils "
This is not bogus. For this package, -dev must be packaged before
the main package, or the latter will get *.h and *.m4 files. Putting
something in packages twice works after all, and we should either
accept its usage fro such cases, or find other solution to do proper
flexible packaging (and that would be a bit hard on syntax. Maybe add
UNFILES?)
--
Best regards,
Paul mailto:pmiscml@gmail.com
next parent reply other threads:[~2007-07-10 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1I8BNL-0002lu-BC@linuxtogo.org>
2007-07-10 9:54 ` Paul Sokolovsky [this message]
2007-07-10 10:29 ` [oe-commits] org.oe.dev packages/glib-2.0/glib.inc : remove bogus ${PN}-dev from packages Graeme Gregory
2007-07-10 10:36 ` Marcin Juszkiewicz
2007-07-10 10:47 ` Richard Purdie
2007-07-10 17:17 ` Justin Patrin
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=986250811.20070710125440@gmail.com \
--to=pmiscml@gmail.com \
--cc=dp@xora.org.uk \
--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.