All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Kevyn-Alexandre Paré" <kapare@rogue-research.com>,
	"Yocto discussion list" <yocto@yoctoproject.org>
Subject: Re: How to add the same recipe twice?
Date: Tue, 10 Jun 2014 08:35:02 -0700	[thread overview]
Message-ID: <539725A6.6020407@linux.intel.com> (raw)
In-Reply-To: <CACgAsMc0XGYRvr8+Y-3DFdTOhonvACuV3K60MkqD59vRp+EWkA@mail.gmail.com>

On 06/09/2014 09:41 AM, Kevyn-Alexandre Paré wrote:
> Hi,
>
> Here what I want to do:
> - Have 2 different psplash in my image.
>
> Here what I have done:
> - Copy and rename the psplash recipe to psplash-desktop and modify
> couple of things.
>
psplash does some interesting package name manipulation, based on what 
additional splash files are being provided.

I am not sure if you are trying to change more than the splash image or not.
>
> Here the warning I'm having:
> WARNING: The recipe psplash-desktop is trying to install files into a
> shared area when those files already exist. Those files and their
> manifest location are:
>     /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/sysroots/overo/pkgdata/runtime/psplash-default
>     Matched in manifest-overo-psplash.packagedata
> manifest-overo-psplash-second.packagedata
This seems to indicate that you might have another recipe called 
psplash-second (maybe a past attempt at this) and it's causing some issues?

Sau!
>     /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/sysroots/overo/pkgdata/runtime/psplash-default.packaged
>     Matched in manifest-overo-psplash.packagedata
>     /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/sysroots/overo/pkgdata/runtime-reverse/psplash-default
>     Matched in manifest-overo-psplash.packagedata
> manifest-overo-psplash-second.packagedata
> Please verify which package should provide the above files.
> WARNING: The recipe psplash-desktop is trying to install files into a
> shared area when those files already exist. Those files and their
> manifest location are:
>     /home/knight/SVN/rogue/3rdParty/Yocto/trunk/starting_point/yocto_build/src/build/tmp/deploy/rpm/armv7a_vfp_neon/psplash-default-0.1+git0+afd4e228c6-r15.armv7a_vfp_neon.rpm
>     Matched in manifest-armv7a-vfp-neon-psplash.package_write_rpm
> Please verify which package should provide the above files.
>
> Here the error:
> http://pastebin.com/t2gYs3WT
>
> Here the diff of my psplash recipe compare to psplash original:
> http://pastebin.com/8TrQRFkQ
>
> In the chat sgw_ recommended my to use:...
> sgw_> kapare, now that I better understand, you want to mv your binary
> in the do_install_append(), and keep the update-alternative code and
> FILES_${PN} bin, but use the renamed binary in the
> ALTERNATIVE_LINK_NAME, but you also need ALTNATIVE_TARGET[psplash] =
> ${bindir}/psplash-default
>
> There is something that I'm missing...
>
> Any idea what?
>
> BR,
>
> -KA
>


  reply	other threads:[~2014-06-10 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 16:41 How to add the same recipe twice? Kevyn-Alexandre Paré
2014-06-10 15:35 ` Saul Wold [this message]
2014-06-10 17:25   ` Kevyn-Alexandre Paré

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=539725A6.6020407@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=kapare@rogue-research.com \
    --cc=yocto@yoctoproject.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.