Hermantha/Brandon: Yes, many spec-files do include a spec-file in the base-specs directory. In the past, we have sometimes built the Sun Desktop stack for Linux, so the design is that the spec-files in the base-specs directory can be used for building on Linux, while the top-level spec-files are used for building Solaris or OpenSolaris packages.
Since the build steps tend to be the same on Linux and Solaris, the %prep, %build and %install sections of the top-level spec-file just calls the appropriate section in the base-specs spec-file. This way, we keep the build as similar as possible when building on either platform, and we only need to manage which patches to apply in one place. That said, we don't really build on Linux anymore, so the two-spec file approach towards writing a spec-file isn't really necessary anymore. You can just write a single spec-file. Brian Hemantha Holla wrote: > Brandon Barker wrote: >> I think I'm almost there, but I'm now getting Deep Recursion messages, >> and it looks like perl will eat up my memory if I don't kill it (after >> 2GB I kill it, as I have another long running process for work on this >> machine that I don't want to die). >> >> What is strange about this is that the recursions seem to be due to >> several things on their own: "%include base.inc" is one of them >> >> This is another: >> %ifarch amd64 sparcv9 >> %include arch64.inc >> %use R_64 = R.spec >> %endif >> >> > > You seem to using R.spec from inside R.spec i.e your R.spec has > something like > '%use R.spec' in it. That may be causing the recursion. > > Check SFEabiword.spec for example. SFEabiword.spec has the line > %use abiword = abiword.spec > > and abiword.spec is in the base-specs folder. > > $ ls spec-files-extra/base-specs/abiword.spec > spec-files-extra/base-specs/abiword.spec > > You could something similar by creating a differently named base-spec. > > > Hemantha > > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org
