Re: License of the contrib plugins

* will guaraldi 

| > | The config.py file allows for a codebase property which will get |
| > inserted at the beginning of the sys path before the PyBlosxom stuff
| > | is imported.  That might cover what you're looking for here in
| > terms | of behavior.
| >
| > The pyblosxom.cgi still needs to know where to find the config file,
| > won't it?
| 
| Oh, I see your issue.  Well, as far as I know we typically tell people
| to put config.py in the directory along-side pyblosxom.cgi.  So then
| it always finds the config.py file.  I'm sure different people do
| different things in that regard, but it's not something we're working
| hard to figure out.

That could work, yes.  (Except that I think it's a tad ugly -- in my
setup, I have ~/err.no/personal/blog being a copy of the pyblosxom.cgi
file and trying to keep the directory clean.

Having .pyblosxom/config.py could work.

Another solution would be a map in /etc/pyblosxom mapping different
.cgi files to different installations and config.py files.  A downside
of this is it requires the cooperation of the local admin to set up a
new installation, but at the same time, you can just symlink and put
the config.py files alongside each other and pyblosxom should be
happy.

| Are you expecting .pyblosxom to be a directory with config.py in it?
| What else would go in there?

It was just a random example so the user can put whatever he wants
there -- I have some plugins I've authored myself there, for
instance.

| One possibility is to add $HOME/.pyblosxom to the path automatically.
| I did that with Lyntin, so I have code that handles the various cases
| (no HOME set, HOME doesn't exist, no .pyblosxom in HOME, ...).
| 
| The problem here is that the web-server needs to be able to read files
| in that .pyblosxom directory.  So then we introduce yet another
| directory to walk people through fixing permissions on.  I don't know
| if anyone really cares about that.  It's something I notify users of
| in the installation guide, but I don't really get into it after that.

Yeah, that part of it sucks, and you can have some sort of shared
installation (where multiple people have write access to the tree)
which then don't really have a home directory as such..

-- 
Tollef Fog Heen                                                        ,''`.
UNIX is user friendly, it's just picky about who its friends are      : :' :
                                                                      `. `' 
                                                                        `-  


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click