5,576
edits
Changes
Jump to navigation
Jump to search
Line 200:
Line 200: − {{note box|please chris can you summary what you are meaning}}+ − + − [15:51:38] Ian Wells: Hopefully the patch applies cleanly to SME9 − [15:51:57] Ian Wells: I find that it is good to do a 'make prep' and see if the patch is OK − [15:51:58] xyz burnat: Am doing local build now, let see − [15:52:04] Ian Wells: Then do a make mockbuild − [15:52:45] xyz burnat: ahhhh Too late, I started the local build, can I do make prep after to check? − [15:53:13] Ian Wells: If the local build works then no worry − [15:53:32] xyz burnat: OK, so either do a make prep or do a local build, yes? − [15:53:40] Ian Wells: Yes − [15:54:11] Ian Wells: Often when using a SME8 patch on SME9 it fails due to a minor issue, eg linenumbers − [15:54:46] Ian Wells: make prep tells you that quicker than make mockbuild and also it shows the problem in the shell rather than having to find the log file − [15:54:55] Ian Wells: However both work.
Rpm build example using cvs/mock (view source)
Revision as of 01:15, 10 February 2014
, 01:15, 10 February 2014→USE PREP TO CHECK PATCH
===USE PREP TO CHECK PATCH===
===USE PREP TO CHECK PATCH===
Often when using a SME8 patch on SME9 it fails due to a minor issue, eg linenumbers, then '''make prep''' tells you that quicker than '''make mockbuild''' and also it shows the problem in the shell rather than having to find the log file.
However both work.
===BUILDING A PACKAGE FROM CVS ON REQUEST===
===BUILDING A PACKAGE FROM CVS ON REQUEST===