Re: [Ltib] About the deployment process / terminology

[Stuart Hughes]

Hi Franz,

I don't mean to be rude, but please ask a question rather than make a
series of assertions and sort-of ask a question.

I'm still not altogether sure what it is you're asking?

Normally package building is controlled by rpm and runs all the stages.
 The tmp staging area is transient.

rpm natively supports -bp (prep) and short-circuit -bc (build) and -bi
(install), but the install only populates the temporary staging area.

scdeploy is a fabrication of LTIB that runs an scinstall to populate the
staging area, and then creates a temporary spec file to build only a
binary package from this area, which is installed into the rootfs (NFS
area).  The purpose is to make it possible to do iterative package
development including target testing.

As far as jffs2 building goes, this happens after and independently of
building packages and the NFS rootfs area.  jffs2 (and RAMdisk) etc are
built by selectively copying the NFS rootfs are to rootfs.tmp and then
using that to create the image file.  If you have not finished your
package development, save yourself a lot of effort and use NFS
deployment.  This way you can edit -> scbuild, scdeploy -> test ->
repeat.  This can be done without any re-boot on your target (usually).

If this doesn't answer your question, please try to ask it a different
way.  e.g. something indicating what it is you want to do, or what is
not happening that you expect to.

Regards, Stuart

Franz TRIERWEILER wrote:
> Hi,
> 
> Spec files define pfx as:
> 
> %define pfx /opt/freescale/rootfs/%{_target_cpu}
> 
> The RPM_BUILD_ROOT variable is initialized by rpm as the value provided
> by tag "BuildRoot" ( %{_tmppath}/%{name} ). rpmbuild sets _tmppath as
> /home/<login>/ltib/tmp' and name is read from the package name tag.
> 
> The RPM_BUILD_ROOT variable is usually passed to make tool by:
> 
> make install prefix=%{_prefix} DESTDIR=$RPM_BUILD_ROOT/%{pfx} when rpm
> enters the installation clause.
> 
> Thus, finally the installation path is
> /home/<login>/ltib/tmp/{name}/opt/freescale/rootfs/%{_target_cpu}/prefix
> (usually, prefix = /usr)
> 
> Once the build is done, my understanding is that this tmp directory
> contains the result of the build, ready to be copied (or "deployed")
> somewhere.
> 
> I would like to know it the deployment process (m -scdeploy) is entirely
> managed by LTIB (and thus unknown to rpm since rpm only builds, and does
> not "deploy") and finally, if the "deployment" terminology only refers
> to the process of feeding ./ltib/rootfs with the new files and updating
> the jffs2 image file?
> 
> Thanks for your help in understanding the LTIB philosophy and process.
> 
> Regards,
> Franz
>