Paul McNett wrote: > Carl Karsten wrote: >>> -> /home/pmcnett/dabo >>> top level dabo directory, the one with AUTHORS and README and (most >>> importantly) the one with the dabo subdirectory (the top-level of the >>> importable dabo stuff). >> So you have /home/pmcnett/dabo/dabo right? > > Yes. What was the problem again?
"dabo dir" is not definitive - it does not identify a dir. makes for crappy docs. > > >> That bothers me. so does dabo/dabo/dabo, which is what I had for a while, >> then >> I switched to dabo/trunk/dabo/dabo, which I don't like either. > > > I actually have: > > ~/dabo-full/ > ~/dabo-full/branches > ~/dabo-full/tags > ~/dabo-full/trunk > > and a symlink: > ln -s ~/dabo-full/trunk dabo > Is that your final answer? > Why are you bothered? The outer Dabo can be named whatever you want, so > change it! That's what I am trying to do, but can't figure out what to change it to. > > cd ~ > svn co http://svn.dabodev.com/trunk Dabo-Outer > I'm not going to change it to Dabo-Outer. :) > It is the interior 'dabo' that is important, because it is the package name. All the dirs are somewhat important. if they aren't, then delete them :) btw - the package name does not have to be the same as the dir name. but making it different would make things more confusing, which is not what I am trying to do. > >> -> /home/pmcnett/dabo >> -> /home/pmcnett/daboide >> -> /home/pmcnett/ss >> >> I think you are going to find your home to become cluttered. Even if works >> for >> you, I don't feel good recommending it. > > Um, yeah, my home directory is always cluttered. But every now and then > I clean house. And I have yet to encounter an actual problem with a > cluttered home directory. I never have trouble finding anything, which > would seem to be the main thing to be concerned about. "be sure to clean house now and then." not sure that should be the official policy :) > > >>> somewhere and importable from Python. It matters not where individuals >>> choose to place their directories, >> true, the docs should make that clear. >> >>> and I'd argue that part of the >>> process of initiation into something like Dabo would be for people to >>> come up with their own best practices themselves. It isn't rocket science. >>> >> So we should just replace the docs with "you figure it out." ? :) > > This is what the docs should say: > > 1) download dabo (use tarball, svn, whatever) > 2) wherever you put it, your choice but write it down, because you need > it in step 3. "write it down"! amusing, but no, the docs should not say that. or anything like that. Not if they don't have to, and they don't. It does get around the funky dir name issue, but I am pretty sure coming up with better dir names is a better solution. > 3) put a dabo.pth file in your python site-packages directory[1] > pointing to the location of your outer dabo directory. So, if you > downloaded to ~/, this would be ~/dabo. wouldn't it be ~/dabo/dabo ? > > > [1] Windows: c:\python2x\lib\site-packages; Linux: > /usr/lib/python2x/site-packages; Mac: > /Library/Frameworks/Python.framework/Versions/2.5/lib/python25.zip python25.zip ? > > >> The day that someone installs Dabo is not the day they should be figuring >> this >> kind of thing out. Good chance they are overwhelmed with things to figure >> out, >> and having a suggested path to follow really helps. Even for seasoned >> python >> programmers, the concept of some abstract classes may be new (I bet most are >> use >> to working with modules) and a seperate dir of tools (like ide) may also be >> new. >> It certainly isn't the normal set of things you get with anything I have >> seen. > > I agree that there should be a simple set of instructions. Then stop with all that "you figure it out" style stuff :) > The easiest > first step is what is described in README: geeze - more docs. I think this is the one project I have seen that has too much docs. > > python setup.py install > > Which works 90% of the time. So the first thing people get is a good What are you basing 90% on? not that I am disagreeing, but I bet you have no idea how many people try it and what the results are. If it really is good enough, why are there all the other docs? > install of dabo, and then they can figure out how to get the .pth thing > working when they get tired of installing dabo when they merely want an > update. > Why won't svn update work? Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
