All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: openembedded-commits@openembedded.org
Subject: Re: [oe-commits] org.oe.dev packages/webkit: Build and package naming fixes (when using debian renaming)
Date: Fri, 26 Oct 2007 06:43:47 +0200	[thread overview]
Message-ID: <47217083.4000103@student.utwente.nl> (raw)
In-Reply-To: <E1IlBjn-00084R-Qk@linuxtogo.org>

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

freyther commit schreef:
> packages/webkit: Build and package naming fixes (when using debian renaming)
>     We do not want the package to be named libwebkitgtk-launcher but want to
>     keep the webkit-gtklauncher names. 

Do we? I created and maintain those recipes, and I made the decision to
name it libwebkitgtk-launcher when using debian naming. I would have
used DEBIAN_NOAUTONAME_webkit-gtklauncher otherwise. Which brings me to
my second point:


> +python populate_packages_prepend() {
> +    print "foooo"
> +    print bb.data.getVar("DEBIAN_NAMES", d, True)
> +    if bb.data.getVar("DEBIAN_NAMES", d, True):
> +        base = bb.data.expand("${PN}launcher", d, True)
> +        bb.data.setVar("PKG_%s" % base, base, d)
> +        bb.data.setVar("PKG_%s-dbg" % base, "%s-dbg" % base, d)
> +}

Using python is unneeded and confusing. And as webkit maintainerin OE, I
don't want those in the recipes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHIXCDMkyGM64RGpERAqZuAKCsK/Dxm1EPgk0qEp+20dixabuHYwCeLTLv
Ztk68CUYd2ByaVgFxEh+67M=
=e/yc
-----END PGP SIGNATURE-----



       reply	other threads:[~2007-10-26  4:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IlBjn-00084R-Qk@linuxtogo.org>
2007-10-26  4:43 ` Koen Kooi [this message]
2007-10-26 13:42   ` [oe-commits] org.oe.dev packages/webkit: Build and package naming fixes (when using debian renaming) Holger Freyther
2007-10-26 22:20     ` Richard Purdie

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=47217083.4000103@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-commits@openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.