<br><br><div class="gmail_quote">On Fri, Jan 16, 2009 at 12:27 PM, Patrick R. Michaud <span dir="ltr"><<a href="mailto:pmichaud@pobox.com">pmichaud@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm not at all opposed to providing pre-packaged downloads,<br>
where select recipes are included as part of the bundle.<br>
However, part of the issue is figuring out where to put them --<br>
if we keep them in "cookbook/", a PmWiki upgrade or downgrade<br>
runs the risk of overwriting someone's (upgraded/modified)<br>
cookbook recipe unexpectedly.<br>
<br>
If we solve that, then we could community-wide select recipes<br>
that are worthy of inclusion in the distribution.<br><br></blockquote></div><br>Perhaps there be a /bundles directory, so a user could just include('/bundle/gallery/bundleconfig.php');...<br>/cookbook/bundles<br>
+--/blog<br>+--/cms<br>+--/gallery<br>....+--bundleconfig.php<br>
....+--somerecipe1.php<br>
....+--somerecipe2.php<br>
....+--somerecipe3.php<br><br>And better yet, use bundleconfig.php in such a way that a user could disable any recipe from config.php. That way, the-average-user could easily upgrade while feeling comfortable that everything will just work.<br>
<br>Mike<br>