<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Oct 28, 2006, at 6:27 AM, Hans wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">All recipes have unique filenames, and we do respect each other in</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Comic Sans MS" size="3" style="font: 12.0px Comic Sans MS">that we are not overwriting each other's files when uploading.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>Some recipes instruct you to change the filename. Sometimes I remove the version number from a filename, because to keep multiple versions on the site people append the version number to the filename. And to update a recipe for a farm with many wikis, I don't necessarily want to change every config.php file for the wikis actively using the recipe -- instead I just change the filename to match the old filename -- blocklist2.83833.php would become bloclist2.php</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>So I disagree about recipe filenames being their unique namespace, or relying on admins keeping the filenames intact after downloading. The version control system should not rely on filenames for versioning.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Crisses</DIV></BODY></HTML>