File: NEWS

package info (click to toggle)
blosxom 2.1.2-2.1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, sid, trixie
  • size: 516 kB
  • sloc: perl: 706; makefile: 15
file content (34 lines) | stat: -rw-r--r-- 1,797 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
blosxom (2.1.0-1) unstable; urgency=low

  This update is a major switch, all local patches have been incorporated
  into upstream version again. Furthermore, html and rss flavours are now
  included in the blosxom script directly and the old 1993 and index
  flavours are not included anymore, to get rid of some further historical 
  annoyances with the packaging.

  MOST IMPORTANTLY: This update adds a new tag into rss feeds:
  <guid isPermanentLink="true"> which helps to notice duplicates and not let
  them appear again for aggregators. Though, for the time of switching it
  might mean that your last entries might appear as new when aggregators
  (like e.g. PlanetPlanet on planet.debian.org) don't check <link> (which
  already should be cached) when finding <guid>. This is unfortunate but not
  really avoidable. To limit impact a new plugin was added: 00RssLimit which
  turns the syndicated feed in only pick up the last 5 entries.

  The plugin timezone got disabled and gets only installed into a new
  /etc/blosxom/plugins-available directory which is the first step to the
  planned blosxom-plugins package. If you found it useful and made use of it
  just symlink it from the plugins directory.

 -- Rhonda D'Vine <rhonda@debian.org>  Fri, 25 Jul 2008 16:19:49 +0200

blosxom (2.0-15) unstable; urgency=low

  The parameter -f for specifying a different configuration file was dropped
  due to security concerns.  It was an illuse of the CGI.pm function.
  It got replaced by a more flexible option:  set the environment variable
  BLOSXOM_CONFIG_FILE to an alternative configuration file you want to use.
  This is especially useful in server contexts where one can use e.g.
  apache's SetEnv directive.

 -- Rhonda D'Vine <rhonda@debian.org>  Fri, 27 Jul 2007 16:49:43 +0200