1 |
On 4 March 2010 20:07, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On Thursday 04 March 2010 19:07:22 Mick wrote: |
3 |
>> > There will be a reason why mysql is being pulled in, most likely a |
4 |
>> > package that must have it. |
5 |
>> |
6 |
>> If a package must have it, wouldn't the USE flag mysql switch to + ? |
7 |
> |
8 |
> Your post seems to indicate a lack of understanding of how these things work. |
9 |
|
10 |
Yep. :-( |
11 |
|
12 |
> Often-times things are not optional, that's what "must" means. USE is |
13 |
> diametrically opposed to that as it has to imply a meaning of "may". If a |
14 |
> package if hard-coded to use mysql, then it must have it, and putting it in |
15 |
> USE in pointless. |
16 |
|
17 |
I see. I thought that (some relevant) USE flags reflected |
18 |
dependencies at some level and that if a dependency changed then this |
19 |
would reflect those USE flags which would now show up as active. So I |
20 |
thought that the mysql USE flag would change from - to +. |
21 |
|
22 |
> There's no rule about this. If mysql is a hard dep, then that's the way it is. |
23 |
> |
24 |
>> > If a user wants postgres, he should install and run postgres. How would |
25 |
>> > this affect the presence or absence of mysql? |
26 |
>> |
27 |
>> Well, I am assuming that if postgres can do what mysql does, then it |
28 |
>> could work in its place. Like if syslog-ng will do what metalog does, |
29 |
>> then the virtual/log-thingie will not insist in pulling in metalog. |
30 |
>> Anyway, the postgres is just an example of asking why are we locking |
31 |
>> down the choice of a database to a particular package/provider. |
32 |
> |
33 |
> Again, you appear to fail to understand. metalog supports a variety of |
34 |
> database backends. Not all apps are like this, some are hard-coded. If you |
35 |
> want to use an app like this, you have no choice but to install mysql. |
36 |
> |
37 |
> If you don't like this, then your choices number two: |
38 |
> |
39 |
> 1. Tough, get over it; |
40 |
> 2. Use a different app |
41 |
|
42 |
No I think you fail to understand what I fail to understand! Ha, ha! :-)) |
43 |
|
44 |
I was not talking about what db a syslog app will use as a back end. |
45 |
I was trying to understand why a virtual package like virtual/mysql is |
46 |
pulling in dev-db/mysql and I used the syslog virtual/real |
47 |
relationship as an analogy. Anyway, I now know two things: |
48 |
|
49 |
a) qt-sql pulled in mysql |
50 |
|
51 |
b) when the wife shouts at me to get going with chores, I do not start |
52 |
an emerge without first checking the contents of it! :-)) |
53 |
|
54 |
Thanks again for your replies. |
55 |
-- |
56 |
Regards, |
57 |
Mick |