Hi Mike, As I tried to explain, rpmbuild natively support short-circuit build/install but do not support a short-curcuit deploy. This is why you have use the "real" .spec file for scbuild/scdeploy but not scdeploy.
Regards, Stuart On 11/11/13 18:44, Mike Nicholson wrote: > Hey Stuart, > > I was under the assumption that I could use the ltib modes - prep, scbuild, > scinstall, scdeploy to test the various parts of my spec file. I wrote the > %prep section and then tested it, wrote the %build and %install section and > tested with scbuild and scinstall modes respectively. When writing the file > section I was running in scdeploy mode to test my file lists without being > forced to recompile a fairly large package every time. Perhaps I am > misunderstanding the purpose of scdeploy. > > I'm just trying to gain a better understanding of the ltib internals so I'm > curious as to why scdeploy rewrites the spec file while scbuild and scinstall > use the original spec file without modification - what was the reason for > this design? > > Thanks for the info. > > Mike > > > On Nov 11, 2013, at 12:47 PM, Stuart Hughes <[email protected]> wrote: > >> 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 >>> [email protected] >>> https://lists.nongnu.org/mailman/listinfo/ltib >>> > > _______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
