On Wed, Dec 22, 2010 at 12:12 PM, Philippe Eveque
<philippe.eveque(a)gmail.com> wrote:
2010/12/22 brett lentz <brett.lentz(a)gmail.com>
>
> On Wed, Dec 22, 2010 at 9:19 AM, Scott Henson <shenson(a)redhat.com> wrote:
>>
>> On Wed, 22 Dec 2010 11:00:26 -0600, <marek.dohojda(a)thomsonreuters.com>
>> wrote:
>> > Actually yes I still am running EL4.
>> > Out of curiosity what do you find is a problem with Cheetah?
>> >
>>
>> Cheetah recently broke on F14 and has had various and other problems
>> with its security. It has generally just been a pain in my back side
>> for some time. I'm not saying I'm going to make a change, just trying
>> to get a general feeling on the subject at this place.
>>
>
>
> Support for EL4 should be maintained until EL4 is EOL. It's only got <2
> years left. I believe it's EOL in 2012.
> As for templating, I agree that there needs to be specific reasons for the
> change. The "various and other" problems should be detailed. It's
possible
> that there are less drastic solutions to those problems.
> I'm not personally invested too heavily in Cheetah. I like Genshi for a
> number of reasons, but would be open to adapting to other options. I'm not
> opposed to learning something new. :-) There's been a few blog posts going
> around Planet Python in the last month about good and bad uses of templating
> engines.
> With cobbler-web having moved to Django for cobbler 2.0 (IIRC), it sort of
> makes sense to move the rest of the app in that direction as well. However,
> if this happens, I think it should incur another big version bump to 2.5 or
> 3.0, so that it's clear that this isn't just a minor update.
sharing the same view.
Thirded, but with the caveat that setting up some transition now would
be good too. We could start moving templates over and still support
cheetah, but eventually all of the templates that ship with cobbler
would be in the new templating language. The only difficulty would be
identifying which kind of template a file is ahead of time.