m (Talk:PackageMaintainers/Join moved to Talk:Join the package collection maintainers: wiki cleanup) |
mNo edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
As a packager new to Fedora's system, and perhaps because I failed to read the output in my terminal, I failed to immediately grok that a 'cvs up' was required after cvs-import.sh but before 'make build' The wording around issuing that command leads one (or at least me) to believe that it is automagically handled by cvs-import.sh, and only necessary if you manually moved files into each branch. Thoughts? --[[User:Ke4qqq|ke4qqq]] 13:28, 19 January 2009 (UTC) | As a packager new to Fedora's system, and perhaps because I failed to read the output in my terminal, I failed to immediately grok that a 'cvs up' was required after cvs-import.sh but before 'make build' The wording around issuing that command leads one (or at least me) to believe that it is automagically handled by cvs-import.sh, and only necessary if you manually moved files into each branch. Thoughts? --[[User:Ke4qqq|ke4qqq]] 13:28, 19 January 2009 (UTC) | ||
In my attempt to be a first time packager, it turned out that you need to do two packages - or review another package - to be sponsored. I didn't budget the time for the 2nd package/review, so had to bow out for a while. Just a heads up for any other busy person wanting to contribute just a few packages. [[User:Sdgathman|Sdgathman]] 02:08, 3 May 2010 (UTC) | |||
<blockquote> | |||
Finally (if you haven't set up an other editor) vi will open up to let you edit the CVS changelog. For the changelog, use the same format as the end of the .spec file | |||
</blockquote> | |||
Really?! This can't be right. --[[User:Spike|Spike]] 18:54, 12 July 2010 (UTC) | |||
Revision as of 18:54, 12 July 2010
As a packager new to Fedora's system, and perhaps because I failed to read the output in my terminal, I failed to immediately grok that a 'cvs up' was required after cvs-import.sh but before 'make build' The wording around issuing that command leads one (or at least me) to believe that it is automagically handled by cvs-import.sh, and only necessary if you manually moved files into each branch. Thoughts? --ke4qqq 13:28, 19 January 2009 (UTC)
In my attempt to be a first time packager, it turned out that you need to do two packages - or review another package - to be sponsored. I didn't budget the time for the 2nd package/review, so had to bow out for a while. Just a heads up for any other busy person wanting to contribute just a few packages. Sdgathman 02:08, 3 May 2010 (UTC)
Finally (if you haven't set up an other editor) vi will open up to let you edit the CVS changelog. For the changelog, use the same format as the end of the .spec file
Really?! This can't be right. --Spike 18:54, 12 July 2010 (UTC)