My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 1: 2 problems, with the plan
1 person starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  vivacar...@gmail.com


 
Project Member Reported by vivacar...@gmail.com, Oct 23, 2007
    2 problems with the plan, 

1) mac osx doesn't come with SVN, it comes with CVS. why not get what they
call the "official version" distributed in a tar, a much easy and safer
option 2) python 2.5 comes with thing you need to run django: sqlite3 ...
thats it. Django comes with a lightweight webserver, 3) according to the
django-announce mailing list, there are backwords incompatible changes
coming to the django development version

Nov 10, 2007
Project Member #1 brianh...@gmail.com
for SVN, lets package the runner with pysvn. This can be seen iDjango sources now.  I
did have a problem running pysvn in wx, so I did some nasty stuff. Nonetheless, it
may still work. I plan on packaging with the current setup.py using py2app that gives
me everything needed in a large .app.

As far as revisions, I think we should still have the UI check out from SVN but not
from the trunk but from the TAG where the official release was built. 

See attachment

Also I am toying with the idea of running Django stand-alone from the python that is
packaged with py2app.  Either way we go, I want to stay away from some of the
problems with shipping large binaries containing already built items.

I know all this goes far away from the original packagemaker project. I keep thinking
we need more than just an installer and more a intaller/monitor/manager program.

Picture 1.png
126 KB   View   Download
Nov 11, 2007
Project Member #2 vivacar...@gmail.com

 so the installer will run script setup.py? post the traceback
Nov 11, 2007
Project Member #3 brianh...@gmail.com
I am not sure if it should run setup.py or just run from the checkout. If it runs
from the checkout, this may be nice because it could also isolate. Better, would be
if it could do either.
Nov 13, 2007
Project Member #4 vivacar...@gmail.com
I think you would have to insite it to run after the checkout, nothing "runs" when
you check something out from svn, thats like "opening safe downloads automatically",
that would be a security issue
Nov 13, 2007
Project Member #5 brianh...@gmail.com
I certainly agree with that. In other words, it should be made clear what is done
from SVN in the form of a warning dialog. "You are about to install Django from SVN,
do you wish to proceed."  Although, It really should be no different from checking
out from SVN from the command line and running setup from there.  We just need to be
sure not to hide the SVN urls.
Nov 13, 2007
Project Member #6 brianh...@gmail.com
I certainly agree with that. In other words, it should be made clear what is done
from SVN in the form of a warning dialog. "You are about to install Django from SVN,
do you wish to proceed."  Although, It really should be no different from checking
out from SVN from the command line and running setup from there.  We just need to be
sure not to hide the SVN urls.
Nov 13, 2007
Project Member #7 vivacar...@gmail.com
This was suppose to be a minimal install right? So first we introduce what django is
supply the warning dialog box upon them clicking the install button, then we check
out the release branch form svn, then we run setup.py then configure it for our
spesifications (using py-sqlite3 and django's provided webserver) and poof! Its
Installed. Now we direct them to the tutorial. Its this all correct?
Nov 23, 2007
Project Member #8 vivacar...@gmail.com
perhaps you could use scapy to build thsi package 
(http://www.secdev.org/projects/scapy/build_your_own_tools.html)
Apr 23, 2008
#9 jason...@gmail.com
Please be aware that SVN is shipped with 10.5.x

Powered by Google Project Hosting