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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Adding additional provides to php database modules
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Adding%20additional%20provides%20to%20php%20database%20modules&In-Reply-To=%3C4F04B299.30009%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010957.html">
<LINK REL="Next" HREF="010959.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Adding additional provides to php database modules</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Adding%20additional%20provides%20to%20php%20database%20modules&In-Reply-To=%3C4F04B299.30009%40gmail.com%3E"
TITLE="[Mageia-dev] Adding additional provides to php database modules">guillomovitch at gmail.com
</A><BR>
<I>Wed Jan 4 21:12:09 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="010957.html">[Mageia-dev] Adding additional provides to php database modules
</A></li>
<LI>Next message: <A HREF="010959.html">[Mageia-dev] Proposal: Cinnamon for Mageia
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10964">[ date ]</a>
<a href="thread.html#10964">[ thread ]</a>
<a href="subject.html#10964">[ subject ]</a>
<a href="author.html#10964">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 04/01/2012 20:08, Oliver Burger a écrit :
>><i> The only problem here is that, pdo aside, there is no unified database
</I>>><i> interface in php. Some applications may have explicit support for some
</I>>><i> databases, this doesn't mean they have generic support for any database.
</I>>><i> You're likely to quickly run into applications able to work with mysql,
</I>>><i> postgresql or sqlite, and those able to work with just mysql or
</I>>><i> postgresql. In theory, you'll end up with as much virtual package as
</I>>><i> potential combination.
</I>><i> I see the problem. So it would be actually better for each application like
</I>><i> drupal and mediawiki to have its own virtual provides for the database
</I>><i> packages (like drupal already does).
</I><pedantism>
"virtual provides" doesn't means anything, because there isn't any
"physical provides". You're speaking of a virtual package here.
</pedantism>
I just had a look at the solution implemented in drupal package. The
drupal-mysql and drupal-postgresql packages seems wrong, because they
enforces a dependency against a local database, whereas it should only
requires the correct pdo package. This small issue aside, the whole idea
seems quite overkill for me: it is really useful to add 3 empty packages
just to handle this interactively, whereas documenting the issue would
be as much efficient ?
BTW, the PDO case is precisely the one for which the package-specific
solution is not needed: any PDO compliant database should work, as PDO
is an abstraction layer :)
--
BOFH excuse #295:
The Token fell out of the ring. Call us when you find it.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010957.html">[Mageia-dev] Adding additional provides to php database modules
</A></li>
<LI>Next message: <A HREF="010959.html">[Mageia-dev] Proposal: Cinnamon for Mageia
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10964">[ date ]</a>
<a href="thread.html#10964">[ thread ]</a>
<a href="subject.html#10964">[ subject ]</a>
<a href="author.html#10964">[ 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>
|
