2009/1/30 ricardo lafuente <[email protected]>: > > i agree with all that has been said; i would make a point of having a > bare-bones, for-servers package (and will gladly take up the task :) > >> I think having a single "official from the website" set of DEB/RPM/TGZ >> packages that has lots of dependencies and doesn't try to require them >> when installed is ideal, so ShoeBot project stays focused.
Okay, two packages from the project itself, "shotbot" (everything) and "shoebot-core"? >> The project ought to encourage people who are publishing scripts in >> the /examples/ folder to make a note in the docstring about the >> dependencies' distro package names in a greppable way. > > i'm wondering if this way of marking up possible dependencies could get > unwieldy ... ximport() ... could point any missing dependencies > according to the modules that running a script would require. Improving ximport() in this way would be excellent! https://code.goto10.org/projects/shoebot/ticket/77 > definitely! But this gets me thinking we ought to have a nightly package > builder while we don't release 0.2. Or at least, something along the lines > of a release candidate. Since i'm doing the docs right now, it will be kind > of necessary to have an up-to-date package for Shoebot. I'll be looking into > this. I think it would be fine for 0.2 to be a shoebot-core release only, since the video/swf export functionality is needed for the latest animation/video stuff to be fully featured. So target the documentation the shoebot-core IMO _______________________________________________ Shoebot-devel mailing list [email protected] http://lists.tinkerhouse.net/listinfo.cgi/shoebot-devel-tinkerhouse.net
