packaging issues
Colin Walters <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Organization | The Debian Project |
| Message-ID | <1053839503.25681.12.camel@columbia> |
Hi, I have created Debian packages, and they are currently waiting in the new package queue to be installed into the archive. However, there are a few issues which if fixed would make my life easier as a packager. One of the first I noticed was pyblosxom has a module named 'libs'. This is a pretty generic name. I was originally going to put the pyblosxom libs/* files in /usr/lib/python2.2/site-packages/, but that would have intruded on the namespace too much, I think. Could we rename 'libs' to 'pyblosxom'? That way other packages can more easily use the classes without having to futz with their sys.path. Secondly, it would be cool if the default pyblosxom.cgi looked for an /etc/pyblosxom/config.py by default. Now, the hairiest issue is plugins. I'm not even sure where to put them. Probably something like /usr/lib/pyblosxom/plugins. Now, what I am thinking of is a setup like Apache2, which uses symlinks to enable/disable plugins (modules). For example, we'd have: /usr/lib/pyblosxom/plugins-available/conditionalhttp.py And then to enable it, the user would do: cd /usr/lib/pyblosxom/plugins-enabled && ln -s ../plugins-available/conditionalhttp.py . Or alternatively, a user would have to explicitly enable plugins in their config.py. I like the former more though. One very minor issue; currently as far as I can tell there is no COPYING or LICENSE file included in the source. The closest I could find was an __license__ = "Python". It would be nice if the full text of the Python license was included in the pyblosxom distribution (and probably would be better from a legalistic standpoint too). Finally, I just want to say thanks for pyblosxom, it was an easy drop-in replacement for blosxom. ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge