Re: [Ltib] scdeploy - why the fabricated spec file?

[Stuart Hughes]

Hi Mike,

scdeploy (short circuit deploy) is a convenience to allow a simple way
to test deploy a package during package development in the same way rpm
natively supports --short-circuit for build/install.  In order to
achieve this you need to fabricate a .spec file based on the true spec
file. IIRC the idea is to build the package with normal rpm build and
the scdeploy rpm is created from the binary output in the staging area
produced by the build.

I don't think there's an easy way around this if you have a complex
.spec file other than letting it install more files than intended during
development testing.  Once your package is working, you can just run a
normal ./ltip -p _package_ and that will use your regular spec file from
start to end.

Regards, Stuart

On 10/11/13 22:50, Mike Nicholson wrote:
> I am fairly new to working with ltib and I was having some issues when
> creating a specfile and running scdeploy.  Running in scdeploy mode was
> causing a failure because the macros defined in the header of my spec
> file appeared to be undefined in the files section despite the macros
> working fine with prep and scbuild.   I now know that this is because
> f_scdeploy creates a temporary spec file and only preserves the %files
> section.
> 
>  
> 
> The files section is fairly complex for this package and I was trying to
> avoid hardcoding some commonly occurring substrings in the files list by
> defining some simple macros in the header. It appears ltib does not
> support this despite the fact that it is commonly used in spec files
> outside of ltib.
> 
>  
> 
> What is the reason for the fabricated spec file when running in scdeploy
> mode?  Is there a better way to avoid repeating myself in the files list
> that adheres to ltib conventions?
> 
> 
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>