Re: License of the contrib plugins

On Mon, 4 Apr 2005, Tollef Fog Heen wrote:
>
> Probably symlink, but yes, that's my initial idea.  If the plugins are 
> then kept in sync with the core, you'll just upgrade both at the same 
> time and hopefully no breakage will occur.

Well, the other reason that the contributed plugins package was separated 
was that we plan on having it on a much shorter release schedule.  So the 
two won't necessarily be in sync.  Though I guess maybe I'm not sure what 
you mean by that.


> | Are you planning on doing up a configuration script (I'm really not
> | familiar with the internals of .deb stuff, but whatever gets kicked
> | off with dpkg-reconfigure) for generating the config.py script and
> | setting up the permissions?
>
> The current packaging of pyblosxom assumes you only have one
> installation and puts the config files in /etc.  This makes sense on a
> small box where you only have one user, but I suspect this isn't the
> most common configuration (and even on my single-user box, I have a
> copy of pyblosxom.cgi copied into my web directory and point that to a
> config.py (which I've written by hand) my home directory.  It then
> uses the rest of pyblosxom, which lives in
> /usr/lib/python2.4/site-packages/Pyblosxom .  This isn't optimal and
> breaks when the API changes.  It'd be really nice if there was a way
> you could have a pyblosxom.cgi which was more or less:
>
> #! /usr/bin/python
>
> import sys
> sys.path.insert(0, "/home/tfheen/.pyblosxom")
> sys.path.append('/usr/lib/python2.3/site-packages/pyblosxom/')
> import config
>
> if __name__ == '__main__':
>    from Pyblosxom.pyblosxom import DTRT
>    DTRT()
>
> (where DTRT is shorthand for Do The Right Thing. :)

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.


> If you have ideas on how it can be done better, I'm all ears. Packaging 
> web applications is very hard in as nobody has yet found a great way of 
> doing it.  (You want it to work out of the box, but you also want the 
> admin to be able to customise and/or disable the application, for a 
> start.)

I hear that.  I'd like to make it easier on everyone (PyBlosxom developers 
and package maintainers for Debian, Gentoo, et al) for this sort of 
thing--both the single-box/single-user case and the single-box/multi-user 
case.

/will


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