From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe-core] Prefix in rpms packages
Date: Mon, 7 May 2012 12:43:36 -0500 [thread overview]
Message-ID: <4FA809C8.1000504@windriver.com> (raw)
In-Reply-To: <CAOHjBZusy84GNLJ+YXY598E4Zd5M-zAZo=hb==wVJhwTQqDPkA@mail.gmail.com>
On 5/7/12 5:30 AM, Giuseppe Condorelli wrote:
> Hi All,
>
> after having built my own image, I've looked at the resultant rpms under
> the deploy directory and I saw
> no relocation is possible (rpm -qpli<package>). This because Prefix is not
> set during spec file creation
> (package_rpm.bbclass).
> As far as you know, is it possible to set Prefix somehow?
What type of packages are you trying to relocate?
For target packages I don't expect that it would ever work. The items built by
the build system often have internal paths and expectations.
For SDK packages (i.e. things that run on the host), it might be possible to
make them relocatable, but it would be specific to those style packages. (Any
relocatable package has to have the inbuilt knowledge to move and change
configuration files as necessary. Also you have to have the right set of
packages to install into the environment and such. I don't believe we use RPM
to install any native/SDK packages today.)
--Mark
> Please let me know.
> Thanks,
> Giuseppe
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-05-07 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 10:30 [oe-core] Prefix in rpms packages Giuseppe Condorelli
2012-05-07 17:43 ` Mark Hatle [this message]
2012-05-08 8:02 ` Giuseppe Condorelli
2012-05-08 12:59 ` Mark Hatle
2012-05-08 14:20 ` Giuseppe Condorelli
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=4FA809C8.1000504@windriver.com \
--to=mark.hatle@windriver.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.