Changes between Version 3 and Version 4 of BittenRecipesExtractorScript
- Timestamp:
- Nov 28, 2011, 10:20:34 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BittenRecipesExtractorScript
v3 v4 19 19 When I have been modifying the scripts using emacs (and possibly some other editors do this), the editor will create a backup swap file, which just so happens to match the file matching routine I have in place for recipes to be committed. I have not seen this cause issues, but it most certainly is not desirable. My advice is to edit a master copy, such as the ones in the subversion directory, and copy those two files, to your recipe directory and use them there.[[BR]] 20 20 21 Super User access is needed when reading and writing to the Trac database directly. Also, on some of my clusters that I work with, multiple version of python can exist. Meaning, if you receive errors like: 21 Super User access is needed when reading and writing to the Trac database directly.[[BR]] 22 Also, on some of my clusters that I work with, multiple version of python can exist. Meaning, if you receive errors like: 22 23 {{{ 23 24 ImportError: No module named trac.env … … 27 28 export PATH=/usr/local/python2.7/bin:$PATH 28 29 }}} 30 ^Note: This, being the one reason I do not include the common #!/usr/bin/python interrupter header in my scripts.^[[BR]][[BR]] 31 29 32 30 33 == Download == … … 53 56 54 57 === Editing the Recipe Files === 55 The file syntax is fairly straight forward. The values are delimited by the two carrot characters.[[BR]] 56 From first value to last: 58 The file syntax is fairly straight forward. The values are delimited by two carrot characters. Please, if there is a quicker better way, do submit a ticket.[[BR]] 59 60 From the first value to last: 57 61 * The unique recipe name (NEVER CHANGE THIS) 58 62 * The path in your repository