Karl Berry wrote: > Ok, seems like we should setup a development instance of Savane, at > least the relevant parts. Does that sound right? > > FWIW, I found it impossible in practice to set up a usable development > instance of Savannah (or Savane). Thus, when I wanted to do experiments > like this, I merely copied the php file in the live directory (on > frontend) to a different name (e.g., editgroupkarl.php) and then worked > on that.
This is exactly what I do as well. I always develop "on the side" of the existing scripts. Then commit them into place once they are ready to be committed to version control. > Otherwise I could have spent my whole life trying to get the development > savannah working, and never made any progress on the actual > problem. Adding in the FSF connection (precisely one of the places where > "Savane" and "Savannah" differ, BTW, as I understood it) and it sounds > even more problematic to get a development instance working. The database content problem is the main issue. > On the other hand, if you want to try, Assaf (Gordon) put a lot of > effort into setting up a development instance, and (afaik) it did work > for him. He documented his process here: > https://savannah.gnu.org/maintenance/FrontEndDevelopmentSite Yep! Bob
signature.asc
Description: PGP signature
