Re: License of the contrib plugins

On Mon, 4 Apr 2005, Tollef Fog Heen wrote:
>
> (No need to Cc me on mails to the list, btw, I'm subscribed. :)

Oops--I had no idea.  Technically, Wari is the only person that can see 
who is subscribed to which mailing list.

> I guess we want to have the latest core and contrib modules working 
> together at all times, so that «in sync» enough for my purposes at 
> least.  If we have some known incompatibilities, that can be handled 
> through the dependency system.  And if we decided to keep API 
> compatibility in 1.x, then break it for 2.x, that policy could easily be 
> expressed in the dependency system too.  (Basically that 1.2 would be a 
> strict superset with no changed semantics over 1.1, so everything that 
> worked with 1.1 worked with 1.2 too.)  This is the API versioning that 
> Gaim is using, at least.

Hrm...  Well, I see us doing more frequent contributed plugin pack 
releases than PyBlosxom core releases as more people use the contributed 
plugins and find issues.  I guess we'll see if that turns into an issue.


> | 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.

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

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.

/will