blob: 9cf6959585294ef711c555c6deefff0313e9cfc5 (
plain)
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
<!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=%3C5003D2AF.5030505%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="017366.html">
<LINK REL="Next" HREF="017371.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] php-smarty vs. php-Smarty</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20php-smarty%20vs.%20php-Smarty&In-Reply-To=%3C5003D2AF.5030505%40gmail.com%3E"
TITLE="[Mageia-dev] php-smarty vs. php-Smarty">guillomovitch at gmail.com
</A><BR>
<I>Mon Jul 16 10:37:03 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="017366.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI>Next message: <A HREF="017371.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17369">[ date ]</a>
<a href="thread.html#17369">[ thread ]</a>
<a href="subject.html#17369">[ subject ]</a>
<a href="author.html#17369">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 16/07/2012 10:31, Colin Guthrie a écrit :
><i> 'Twas brillig, and Oliver Burger at 16/07/12 09:28 did gyre and gimble:
</I>>><i> Am 16.07.2012 08:59, schrieb Oliver Burger:
</I>>>><i> But do you know, if there's software calling for the lowercase name?
</I>>>><i> So we do not fix it for some but break it for others.
</I>>>><i>
</I>>><i> A thought that ocurred to me about this:
</I>>><i> We could rename those folders to the upper case (when Fedora and Suse do
</I>>><i> it that way and most other problems using smarty search for it) and
</I>>><i> provide a symlink to the lower case name so we don't break compatibility.
</I>>><i>
</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>Using README.urpmi for advertising development-specific information is
overkill. The amount of information sent by this media to end user
should be kept minimal, and stay focused on mandatory informations only.
--
You will always forget the most important item if you don't make a list
-- Murphy's Food Laws n°10
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="017366.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI>Next message: <A HREF="017371.html">[Mageia-dev] php-smarty vs. php-Smarty
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17369">[ date ]</a>
<a href="thread.html#17369">[ thread ]</a>
<a href="subject.html#17369">[ subject ]</a>
<a href="author.html#17369">[ 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>
|
