From Fedora Project Wiki
20 September 2016
- 00:2400:24, 20 September 2016 diff hist +1,386 How to create an RPM package Flesh out building GNU Hello to the point of generating %files.
19 September 2016
- 23:1623:16, 19 September 2016 diff hist −2,251 How to create an RPM package Remove this section; replace later with a note about fedpkg clone -a.
- 23:1423:14, 19 September 2016 diff hist −530 How to create an RPM package Remove the licensing section; it wasn't even true.
- 23:1323:13, 19 September 2016 diff hist +102 How to create an RPM package More macro text tweak.
- 22:5522:55, 19 September 2016 diff hist +26 m How to create an RPM package Also ignore complaints about lack of URL.
- 22:5422:54, 19 September 2016 diff hist 0 m How to create an RPM package Fix typo
- 22:5322:53, 19 September 2016 diff hist +75 How to create an RPM package Note that %install is just a shell script.
- 22:5222:52, 19 September 2016 diff hist +180 How to create an RPM package Note that most sections have shell code.
- 22:4922:49, 19 September 2016 diff hist +2,861 How to create an RPM package Start in on %prep.
- 22:0422:04, 19 September 2016 diff hist +157 How to create an RPM package Add note at the point where the old docuent begins.
- 21:2121:21, 19 September 2016 diff hist +1 m How to create an RPM package Fix errant quotes and typo.
- 20:5020:50, 19 September 2016 diff hist +5 m How to create an RPM package No edit summary
- 20:4820:48, 19 September 2016 diff hist +4 How to create an RPM package Script should be mode 644 to avoid an rpmlint complaint.
- 20:4220:42, 19 September 2016 diff hist −65 How to create an RPM package Start working on a more complex example.
- 20:0220:02, 19 September 2016 diff hist +1,094 How to create an RPM package Add fedora-review section
- 19:0619:06, 19 September 2016 diff hist +363 How to create an RPM package Add fedora-packager-setup and note that root is no longer needed.
- 19:0019:00, 19 September 2016 diff hist +378 How to create an RPM package Add mock and koji.
- 18:5518:55, 19 September 2016 diff hist +4,744 How to create an RPM package And that should be all of the basic instructions
- 17:4017:40, 19 September 2016 diff hist +233 How to create an RPM package Explain curlies around macros.
- 17:1017:10, 19 September 2016 diff hist +35 m How to create an RPM package Start of next section
- 17:0917:09, 19 September 2016 diff hist +772 How to create an RPM package Final build instructions.
- 16:5516:55, 19 September 2016 diff hist −16 m How to create an RPM package Clean up.
- 16:4616:46, 19 September 2016 diff hist +662 How to create an RPM package Almost done building the first package.
- 16:1616:16, 19 September 2016 diff hist +2,042 How to create an RPM package More stuff.
- 15:2915:29, 19 September 2016 diff hist +73 How to create an RPM package Indicate specfile naming.
- 15:2815:28, 19 September 2016 diff hist +1,126 How to create an RPM package More first steps, actually build a (useless) package.
- 14:5214:52, 19 September 2016 diff hist +209 How to create an RPM package Note that we assume you can drive an editor and know how to build what you want to package.
- 14:4714:47, 19 September 2016 diff hist +87 m Packaging:Guidelines Add revision information at the top.
- 14:3514:35, 19 September 2016 diff hist +179 m Packaging:Guidelines Add note that rpmdevtools may diverge from the guidelines, and that others may maintain "your" packages.
- 14:1214:12, 19 September 2016 diff hist −2,988 How to create an RPM package Begin a "first steps" section, nuke old section listing too much useless stuff.
- 13:4613:46, 19 September 2016 diff hist −556 How to create an RPM package Fix usermod call; remove section about timestamps as we'll use spectool later to handle that.
- 13:4313:43, 19 September 2016 diff hist +36 How to create an RPM package Redo introduction and disclaimer.
- 02:5102:51, 19 September 2016 diff hist +572 How to create an RPM package Reorg terminology section.
17 September 2016
- 19:1219:12, 17 September 2016 diff hist −1 m How to create an RPM package The scriptlets page documents more than just "post scripts".
16 September 2016
- 23:5323:53, 16 September 2016 diff hist +20 m How to create an RPM package Add a bit of margin to the TOC.
- 23:3823:38, 16 September 2016 diff hist +1 How to create an RPM package No edit summary
- 23:3723:37, 16 September 2016 diff hist +1,215 How to create an RPM package Start adding terminology and use the package template.
- 18:5318:53, 16 September 2016 diff hist −1 m Packaging:Naming Don't instruct packagers to use a dash followed by a suffix containing a dash.
- 18:4618:46, 16 September 2016 diff hist −94 m Package Review Process More cleanup; the HTML list syntax wasn't necessary.
- 18:4418:44, 16 September 2016 diff hist +30 m Package Review Process Clean up; note that the review ticket shouldn't be referenced in later bodhi updates.
- 18:4118:41, 16 September 2016 diff hist −42 m Package Review Process Move authorship info to the bottom.
- 18:3618:36, 16 September 2016 diff hist +90 Package Review Process Indicate the actual bug to use when filing SCM requests for exempted packages.
- 18:2618:26, 16 September 2016 diff hist +393 Packaging:Naming Add note that is generally acceptable to use descriptive suffixes instead of versions, and include caveats.
- 03:1603:16, 16 September 2016 diff hist +32 m How to create an RPM package Better descrption of possible issues during this rewrite.
15 September 2016
- 22:1622:16, 15 September 2016 diff hist +454 Talk:How to create an RPM package →Big restructuring: new section
- 22:1322:13, 15 September 2016 diff hist +287 How to create an RPM package More cleanup, add under construction notice.
- 21:5521:55, 15 September 2016 diff hist −32 How to create an RPM package Restructure and prepare to use fedpkg for everything.
- 21:3921:39, 15 September 2016 diff hist −1 m How to create an RPM package "RPMs", not "RPM's".
- 21:3921:39, 15 September 2016 diff hist +63 How to create an RPM package Clean up a bit; fix grammar.
- 21:3221:32, 15 September 2016 diff hist +42 How to create an RPM package Correct some links, mention that the utilities used will also be Fedora-specific.