This is a request to create or update documentation about this project.
As I said in r44: "While I agree that there should be a Developer Install document, I think that it should be a text file or HTML file.
Personally, I think that the current Google Code Wiki engine sucks. That's why I removed the wiki tab from this site."
The developers install file should be put into the .tar file created by the setup.py so that it is in all the source code downloads, but not in the released version of the application installer.
When this is completed, I will add this document to the [http://l5rnw.com L5RNW site] as well.
Comment #1
Posted on Jan 5, 2009 by Swift PandaI'll get this formatted over as a plaintext document unless there is a preference for a rich text format.
Comment #2
Posted on Jan 5, 2009 by Helpful KangarooSwell.
Plain text is probably better as it's more universal.
Comment #3
Posted on Jan 6, 2009 by Swift PandaNew documentation for developer install has been created and commited to the database as r47 .
Please review the documentation for errors and changes.
Comment #4
Posted on Jan 6, 2009 by Helpful KangarooCan you make sure that this gets added to the .tar file of source code.
Looks good, thanks
Comment #5
Posted on Jan 7, 2009 by Swift PandaI created a new eopk-0.8.7beta-src.tar.gz file with the new docs directory. I deprecated the old 0.8.7beta source archive. I attempted to upload the new archive but I can not authenticate on the uploads area of the project.
Neither my google account/password nor my google code password are working so I can not upload the file.
Comment #6
Posted on Jan 7, 2009 by Helpful KangarooYou couldn't upload, but you could deprecate? Seems that the two would require the same logged in status.
Anyhow, don't worry about it for now. Check this all in, and I'll post the newest version when we build it.
Comment #7
Posted on Jan 7, 2009 by Swift PandaNoob Alert:
I'm using Eclipse with the SVN plug-in. I have access to the repository, I can check it out to a local copy on my system, I can make changes, I can commit those changes.
I have no option of "checking in".
Also, are you building the tar file manually or do you have a process that is taking care of that?
How do you do your compiling and testing? Do you just run the program from within your editor? Eclipse makes .pyc files in the same directory that I've "checked out" to. Should I be checking out to a different directory? Copying things across? I've been careful to make sure that the .pyc files are excluded from being committed.
Really sorry for all these questions.
Comment #8
Posted on Jan 7, 2009 by Helpful KangarooDone and Done. Thanks Bryan.
Status: Fixed
Labels:
Type-Documentation
Component-Docs
Priority-Low