On Fri, 5 Mar 2010 06:53:15 +, Mick wrote:
I was trying to understand why a virtual package like virtual/mysql is
pulling in dev-db/mysql and I used the syslog virtual/real
relationship as an analogy.
The clue is in the name of the virtual, it is satisfied by one of the
MySQL packages in
On 5 March 2010 09:42, Neil Bothwick n...@digimed.co.uk wrote:
On Fri, 5 Mar 2010 06:53:15 +, Mick wrote:
I was trying to understand why a virtual package like virtual/mysql is
pulling in dev-db/mysql and I used the syslog virtual/real
relationship as an analogy.
The clue is in the name
I am trying to understand what is pulling in mysql again. This
morning a load of qt packages were being updated and I noticed a bunch
of perl and virtual packages in there too. Rest assured dev-db/mysql
was in there, again. This is despite the fact that the mysql use flag
seem to be not active
On Thursday 04 March 2010 17:37:23 Mick wrote:
I am trying to understand what is pulling in mysql again. This
morning a load of qt packages were being updated and I noticed a bunch
of perl and virtual packages in there too. Rest assured dev-db/mysql
was in there, again. This is despite the
On Thu, 4 Mar 2010 17:57:15 +0200, Alan McKinnon wrote:
The tool you want to answer this question is
emerge -t
There will be a reason why mysql is being pulled in, most likely a
package that must have it.
I notice qt-sql is in the list, does that have the mysql flag forced on?
--
On 4 March 2010 15:57, Alan McKinnon alan.mckin...@gmail.com wrote:
On Thursday 04 March 2010 17:37:23 Mick wrote:
I am trying to understand what is pulling in mysql again. This
morning a load of qt packages were being updated and I noticed a bunch
of perl and virtual packages in there too.
On Thu, 4 Mar 2010 17:07:22 +, Mick wrote:
The tool you want to answer this question is
emerge -t
Right, but I started this mammoth emerge before I spent enough time
looking at its contents I'm afraid.
The use emerge --depclean -pv dev-db/mysql
There will be a reason why mysql
Since you already merged it in:
# equery depends mysql
then unmerge or correct USE flags for dependent apps.
To have portage error out instead of merging mysql in the future:
# echo dev-db/mysql /etc/portage/package.mask/I_said_no_mysql
HTH,
Roy
On Thursday 04 March 2010 19:07:22 Mick wrote:
There will be a reason why mysql is being pulled in, most likely a
package that must have it.
If a package must have it, wouldn't the USE flag mysql switch to + ?
Your post seems to indicate a lack of understanding of how these things work.
On Thu, 4 Mar 2010 22:07:14 +0200, Alan McKinnon wrote:
Again, you appear to fail to understand. metalog supports a variety of
database backends. Not all apps are like this, some are hard-coded. If
you want to use an app like this, you have no choice but to install
mysql.
If you don't
On 4 March 2010 20:07, Alan McKinnon alan.mckin...@gmail.com wrote:
On Thursday 04 March 2010 19:07:22 Mick wrote:
There will be a reason why mysql is being pulled in, most likely a
package that must have it.
If a package must have it, wouldn't the USE flag mysql switch to + ?
Your post
11 matches
Mail list logo