<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] php-smarty vs. php-Smarty
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20php-smarty%20vs.%20php-Smarty&In-Reply-To=%3C20120716093228.GM21938%40mars-attacks.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="017373.html">
<LINK REL="Next" HREF="017377.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] php-smarty vs. php-Smarty</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20php-smarty%20vs.%20php-Smarty&In-Reply-To=%3C20120716093228.GM21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] php-smarty vs. php-Smarty">boklm at mars-attacks.org
</A><BR>
<I>Mon Jul 16 11:32:28 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="017373.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI>Next message: <A HREF="017377.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17374">[ date ]</a>
<a href="thread.html#17374">[ thread ]</a>
<a href="subject.html#17374">[ subject ]</a>
<a href="author.html#17374">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Mon, 16 Jul 2012, Oliver Burger wrote:
><i> Am 16.07.2012 10:37, schrieb Guillaume Rousse:
</I>>><i> Le 16/07/2012 10:31, Colin Guthrie a écrit :
</I>>>><i> 'Twas brillig, and Oliver Burger at 16/07/12 09:28 did gyre and gimble:
</I>>>>><i> We could mention in the README.urpmi that the lower case folder name is
</I>>>>><i> deprecated and will be removed in the future, so people do have some
</I>>>>><i> time to change it in their web applications.
</I>>>>><i>
</I>>>>><i> WDYT?
</I>>>><i>
</I>>>><i> This seems like the best solution overall.
</I>>><i> Using README.urpmi for advertising development-specific information is
</I>>><i> overkill. The amount of information sent by this media to end user
</I>>><i> should be kept minimal, and stay focused on mandatory informations only.
</I>><i> Well, this change could very well break self built web applications, so we
</I>><i> should tell people about it, shouldn't we?
</I>><i> So what way for telling people about it do you propose if not using
</I>><i> README.urpmi?
</I>
It can be added to Mageia 3 Release Notes.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="017373.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI>Next message: <A HREF="017377.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17374">[ date ]</a>
<a href="thread.html#17374">[ thread ]</a>
<a href="subject.html#17374">[ subject ]</a>
<a href="author.html#17374">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>