2014-05-09 09:37:28 by Thomas Klausner | Files touched by this commit (553) |
Log message:
Mark packages that are not ready for python-3.3 also not ready for 3.4,
until proven otherwise.
|
2014-01-25 11:30:32 by Thomas Klausner | Files touched by this commit (533) | |
Log message:
Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
|
2013-07-31 12:20:27 by Hauke Fath | Files touched by this commit (3) | |
Log message:
Updating www/py-blosxom to v1.5.3.
What's new in 1.5.3 (July 2013)
===================================
1. Minor fixes
2. Updated and improved documentation
3. Several plugin fixes and updates including Tags, Pagination, and
Ajax comments
4. Improved tests
|
2012-10-28 07:31:10 by Aleksej Saushev | Files touched by this commit (600) |
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
|
2012-08-10 17:04:32 by Hauke Fath | Files touched by this commit (1) |
Log message:
The pyblosxom maintainer changed, and with him the project's home.
XXX Pull-up candidate, I guess?
|
2012-01-27 08:04:52 by OBATA Akio | Files touched by this commit (1) |
Log message:
Any of compiler languages are not required to build.
|
2012-01-26 20:52:57 by Hauke Fath | Files touched by this commit (1) |
Log message:
pyblosxom 1.5 requires Python 2.[5..7]
|
2012-01-12 13:23:58 by Hauke Fath | Files touched by this commit (3) | |
Log message:
Upgrade package to 1.5.2. From WHATSNEW:
What's new in 1.5.2 (December 2011)
===================================
Pertinent to users:
1. Fixed a warning that pops up when doing ``pip install pyblosxom``
2. Removed debug logging from pycategories
What's new in 1.5.1 (December 2011)
===================================
Pertinent to users:
-------------------
1. Fixed a problem with the manifest so ``python setup.py install``
works again.
2. Fixed the WHATSNEW so it shows correct version and date for
1.5 release.
What's new in 1.5 (December 2011)
=================================
Pertinent to users:
-------------------
1. Renamed the project from PyBlosxom to Pyblosxom (no more CamelCase).
2. I moved all the plugins again. This time, instead of being in
``plugins/``, they're now in ``Pyblosxom/plugins/``.
You no longer have to copy core plugins into your plugins
directory. Instead of copying core plugin files, refer to the
plugins in your ``config.py`` file using their full Python path in
the Pyblosxom package.
For example, the pycalendar plugin is now in
``Pyblosxom/plugins/pycalendar.py`` and thus its Pyblosxom
package path is ``Pyblosxom.plugins.pycalendar``. Your
``config.py`` file would look have this::
py["load_plugins"] = [
...
"Pyblosxom.plugins.pycalendar",
...
]
If you do this, then the next time you upgrade PyBlosxom, the
plugins will be upgraded automatically.
Further, documentation for plugins is at the top of the individual
plugin files, but also in the documentation. This includes a list
of the plugins available in the core.
.. only:: text
You can see the plugin documentation in docs/plugins/.
.. only:: html
You can see the plugin documentation at :ref:`part-two`.
3. Plugins added: markdown_parser, readmore
4. Plugins changed:
pages
* Fixed documentation and error messages for ``pagesdir``.
* Fixed frontpage checking. Should catch / as well as /index
now.
* Adds more examples to documentation.
tags
* Increased tag cloud range from 3 sizes to 5.
* Adds truncate support.
* Fixes problems with initialization when building tags so that
it initializes plugins allowing them to do startup things.
This fixes problems with plugins that augment entry parsers.
rst
* renamed it to rst_parser so it's clearer what it is
pycategories
* fixed category_start/category_begin behavior for root category
* fixed the first example of settings in the documentation
the rest of the plugins: pep8 fixes and documentation updates
5. Plugins removed from Pyblosxom: commentAPI
6. Fixes error handling for loading plugins. When doing
``pyblosxom-cmd test`` and a plugin fails to load, it'll now tell
you. When using the debug renderer and a plugin fails to load,
it'll now tell you.
7. Lot of work on simplifying and improving the documentation.
8. Added a ``static_yearindexes`` setting. Set it to True to generate
year indexes and False to not generate year indexes.
Pertinent to developers
-----------------------
1. I removed all the extra infrastructure for testing plugins.
Plugins that come with the core are now in the Pyblosxom package
and their tests are in ``Pyblosxom/tests/``.
2. Adds *generate* subcommand to pyblosxom-cmd. This makes it easier
to test blogs and plugins that do things with entries.
3. Renamed ``PyBlosxomWSGIApp`` class to ``PyblosxomWSGIApp``.
4. Renamed ``PyBlosxom`` class to ``Pyblosxom``.
5. Moved the project from gitorious to github. The new git repository
is at `<http://github.com/willkg/pyblosxom>`_.
6. Removed ``VERSION_DATE`` and ``VERSION_SPLIT``. They're kind of
silly and don't really help much.
I moved the version to ``Pyblosxom/_version.py``. Use it like
this::
from Pyblosxom import __version__
print __version__
I updated the documentation accordingly.
|
2011-07-08 16:38:34 by Hauke Fath | Files touched by this commit (2) |
Log message:
Better catch the PLIST changes, too...
|
2011-07-08 11:59:19 by Hauke Fath | Files touched by this commit (2) | |
Log message:
Update to Blosxom 1.5rc3.
What's new in 1.5 rc3
=====================
Pertinent to users:
-------------------
1. PyBlosxom shows an error page if it crashes rather than forcing
you to go figure out what happened by finding the web server logs.
This should make configuring and debugging much easier.
2. Bunch of new plugins.
3. Bunch of fixes to the comments plugin, tags and pycalendar plugins.
Tags plugin gains tags cloud functionality.
Comments plugin gains comment_disable_after_x_days feature.
If you're using them, update to the latest versions.
4. Bunch of fixes to the documentation. If you see errors or things
that are unclear, let us know.
The documentation for the comments plugin still needs to be overhauled.
5. Bunch of other bug fixes.
6. Bunch of new plugins: magicword, pages, rst, check_nonhuman, and
check_blacklist.
|