Edgewall Software

Changes between Version 26 and Version 27 of ClearSilver


Ignore:
Timestamp:
Jan 17, 2015, 4:38:04 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • ClearSilver

    v26 v27  
    1 = ClearSilver =
     1= ClearSilver
    22
    3 '''Clearsilver''' (http://www.clearsilver.net/) is a powerful and flexible HTML templating engine.
     3[http://www.clearsilver.net/ Clearsilver] is a powerful and flexible HTML templating engine.
    44----
    5 Clearsilver has its drawbacks, and after a few years of successful (but sometimes frustrating) use, the TracTeam unanimously--and enthusiastically!--decided to go for another templating engine: '''[http://genshi.edgewall.org Genshi]'''.
    6 
    7 Therefore, starting with [milestone:0.11], Trac will no longer ''require'' Clearsilver. However, through 0.12 Trac will retain the infrastructure needed to support plugins using Clearsilver.
     5Clearsilver has its drawbacks, and after a few years of successful but sometimes frustrating use, the TracTeam unanimously--and enthusiastically!--decided to switch to another templating engine: '''[http://genshi.edgewall.org Genshi]'''.
     6Starting with [milestone:0.11], Trac will no longer ''require'' Clearsilver. However, through 0.12 Trac will retain the infrastructure needed to support plugins using Clearsilver.
    87
    98Plugin developers should nonetheless consider switching to Genshi during the transition phase of 0.11 development.
    10 See ["TracDev/ApiChanges/0.11#MigratingawayfromClearsilver"]
     9See ["TracDev/ApiChanges/0.11#MigratingawayfromClearsilver"].
    1110
    1211Trac 0.12 still contains the Clearsilver supporting code, although the code is no longer supported.
    … …  
    1615----
    1716
    18 == Download ==
     17== Download
    1918
    20 Official [http://www.clearsilver.net/downloads downloads]
     19Official [http://www.clearsilver.net/downloads Clearsilver downloads].
    2120
    2221For Python 2.5, you need to build the package yourself, and you probably need the following patch: googlegroups:trac-users:5b502b38f4e13c8f
    2322
    24 Furthermore for Python 2.5 on Win32 there is an egg build (and instructions) at http://tn123.ath.cx/clearsilver/
     23Furthermore, for Python 2.5 on Win32 there is an egg build and instructions at http://tn123.ath.cx/clearsilver/.
    2524
    26 == Building the package yourself ==
     25== Building the package yourself
    2726
    28 If you have to build the package yourself, be sure
    29 to build a '''thread-safe''' version of the library.
     27If you have to build the package yourself, be sure to build a '''thread-safe''' version of the library.
    3028There's no explicit configuration switch for that.
    31 Just pay attention to the ''Checking pthread.h... yes''
    32 line during configuration. If it's ''no'', then you'll
    33 have to fix the configuration step yourself
    34 (see that [/trac/ticket/1764#change_15 comment]).
     29Just pay attention to the ''Checking pthread.h... yes'' line during configuration. If it's ''no'', then you'll have to fix the configuration step yourself, see that [/trac/ticket/1764#change_15 comment].
    3530
    36 Non thread-safe builds have been reported to '''not'''
    37 work with Trac in a multi-threaded setup
    38 (see the comment linked above).
     31Non thread-safe builds have been reported to '''not''' work with Trac in a multi-threaded setup, see the comment linked above.
    3932
    4033On `x86_64` platforms, the 0.10.x series is needed.
    41 For gcc4, the latest release (0.10.2) should be used. (Should this page be updated to reflect 0.10.4?)
     34For [https://gcc.gnu.org/ gcc4], Trac release 0.10+ should be used.
    4235
    43 === ClearSilver 0.10.2 ===
     36=== ClearSilver 0.10.2
    4437
    45 There's a typo in the configure scripts.
    46 You'll need to apply the following patch first:
     38There's a typo in the configure scripts. You'll need to apply the following patch first:
    4739{{{
    4840#!diff
    … …  
    7365}}}
    7466
    75 Then, you can call `configure`, for example like this:
     67Then you can call `configure`, for example like this:
    7668{{{
    7769./configure --prefix=/opt/clearsilver-0.10.2 \
    … …  
    8072}}}
    8173
    82 At this point, `make && make install` should work. (Be Warned: Should is very relative).
     74At this point `make && make install` should work. Caution: 'should' is relative.
    8375
    8476Note for *BSD: you may have to use GNUmake by using `gmake` because `make` may not work.
    8577
    86 Note for x86_64 Linux:  ClearSilver is known not to compile on RHEL 4.x x86_64. The ClearSilver developers have not responded except to occasionally nuke threads on their mailing list about the topic... Consider using Trac .11-devel instead. (This might no longer be true for clearsilver 0.10.5, I've compiled & installed without issue on x86_64)
     78Note for x86_64 Linux:  ClearSilver is known not to compile on RHEL 4.x x86_64. The ClearSilver developers have not responded except to occasionally nuke threads on their mailing list about the topic. Consider using Trac 0.11-devel instead. (This might no longer be true for clearsilver 0.10.5, I've compiled & installed without issue on x86_64)
    8779
    88 Useful thread here on Python2.5 and Clearsilver10.3, covers compiling and making things work on x86_64. https://launchpad.net/ubuntu/+source/clearsilver/+bug/86685
     80Useful thread here on Python2.5 and Clearsilver10.3, which covers compiling and configuring on x86_64: https://launchpad.net/ubuntu/+source/clearsilver/+bug/86685