On Wed, 27 Aug 2008, felix winkelmann wrote:
Hi!
Ok, how are we going to proceeed? One can convert and install
eggdoc-based documentation in the setup script (manually).
Or we just handle it like in the old chicken-setup. But we need
a new idea for online docs that are based on eggdoc. egg-post-commit
should go (or only be kept for pre 4 chickens), so this has to be
handled by a different periodical task. Any suggestions or
preferences?
my 2c. i dont think that it should be too difficult to set properties on the
svn commit itself and configure the server to handle them in realtime (at
commit), rather than via a periodical task. this could allow significantly
faster update of eggs when fixes are made, and give some added flexibilities.
if a scheme like this were implemented, getting the docs from the wiki would
actually be more of a pain than the upload...
-elf
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
