CentOS - Dec 2010 - noob question about mock

Hi,

Been recently more and more tempted to use mock for building rpms, but 
looking at it I have one problem. As far as I could read about it, mock 
essentially rebuilds srpms so to use it I would need a separate
"classical"
build environment to create those srpms in the first place.
Am I right or did I get something terribly wrong?


Cheers!

--
Nux!
www.nux.ro

On Thu, Dec 30, 2010 at 8:51 AM,  <nux at li.nux.ro>
wrote:
> Hi,
>
> Been recently more and more tempted to use mock for building rpms, but
> looking at it I have one problem. As far as I could read about it, mock
> essentially rebuilds srpms so to use it I would need a separate
"classical"
> build environment to create those srpms in the first place.
> Am I right or did I get something terribly wrong?
You can use rpmbuild -bs --nodeps to build the SRPM without the
dependency checking. The SRPM is just a compilation of the spec,
source code, and patches.

Ryan

Hi,

On Thu, 2010-12-30 at 13:51 +0000, nux at li.nux.ro
wrote:
> As far as I could read about it, mock 
> essentially rebuilds srpms so to use it I would need a separate
"classical"
> build environment to create those srpms in the first place.
> Am I right or did I get something terribly wrong?
Since CentOS is an rpm based system you will almost always be rebuilding
from srpms and *not* from plain tar balls. Repos catering for
RHEL/CentOS/Fedora provide srpms by default.

However, if you want to make your own (s)rpms or patch existing ones you
will indeed need a "classical" build environment to do so. And since
there are a couple of packages that mock will not build you will need a
fallback build environment for such cases.

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research

On 12/30/2010 05:51 AM, nux at li.nux.ro wrote:
> Been recently more and more tempted to use mock for building rpms, but
> looking at it I have one problem. As far as I could read about it, mock
> essentially rebuilds srpms so to use it I would need a separate
"classical"
> build environment to create those srpms in the first place.
> Am I right or did I get something terribly wrong?
You can always use "mock --shell" to use the mock environment as your 
interactive build environment.