From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to alter ./configure flags from emerge
Date: Thu, 24 Nov 2005 14:44:05 +0100 [thread overview]
Message-ID: <4385C3A5.6050206@planet.nl> (raw)
In-Reply-To: <8764qib0g2.fsf@newsguy.com>
Harry Putnam schreef:
>
> Since syncing yesterday and emerge -u world, I now get
> mysql-5.0.16-r1 when I emerge mysql. It doesn't have the docs built
> either regardless of what USE variable are in force.
Are there in fact docs available for this version yet? From MYSQL, I
mean, not Gentoo. Perhaps that's why you haven't been able to find such
a separate package-- it doesn't yet exist, because the 'source' (the
docs themselves) don't. Worth checking, anyway.
>
> I've took the tips about /etc/portage/package.use syntax and
> arrangement so it now is correct (I think): cat
> /etc/portage/package.use
>
> mail-mta/sendmail mbox sasl milter dev-db/mysql mysql mysqli doc
> ndb-doc dev-backup/bacula mysql mysqli doc
Except that most of those flags are no longer valid for the unstable
version...
ACCEPT_KEYWORDS="~x86" emerge -pv mysql
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] dev-db/mysql-5.0.16-r2 -berkdb -big-tables -cluster
-debug -extraengine -minimal +perl (-selinux) +ssl -static -utf8
>
>
> But now I've got worse provlems than no documentation. I can't even
> start this install of mysql.
>
> /etc/init.d/mysql status * status: stopped
>
> /etc/init.d/mysql start * working on 0 * Starting mysqld0
> (/etc/mysql/my.cnf) ... .......... * MySQL NOT started (0)
>
> Here is where the docs would be quite handy...
The ChangeLog suggests that you may have missed a step or two, or
perhaps should reconsider that "~arch" setting in this case:
less /usr/portage/dev-db/mysql/ChangeLog
# ChangeLog for dev-db/mysql
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-db/mysql/ChangeLog,v 1.266
2005/11/23 19:44:22 vivo Exp $
*mysql-5.0.16-r2 (23 Nov 2005)
23 Nov 2005; Francesco Riosa <vivo@gentoo.org> mysql-4.1.15.ebuild,
mysql-4.1.15-r30.ebuild, -mysql-5.0.16-r1.ebuild, +mysql-5.0.16-r2.ebuild,
mysql-5.0.16-r30.ebuild:
fix Bug #113352 , mysql-5.0.16-r1 does not create
/usr/lib{64}/libmysqlclient.so.15 symlink
==>The linkage has been somewhat improved too. It has been moved in
==>pkg_postinst() function to advise the user to use "revdep-rebuild"
with the
==>right --so-name option.
As a consequence it does not rely on "dosym" but use "ln" program
directly(bug).
==>it work now with FEATURES="prelink notitles sandbox strict userpriv
==>usersandbox keeptemp keepwork" but in the future may be needed to
advise
sandbox that we are messing up with the live file-system
*mysql-5.0.16-r1 (23 Nov 2005)
23 Nov 2005; Francesco Riosa <vivo@gentoo.org> files/mysql-slot.rc6,
-mysql-5.0.16.ebuild, +mysql-5.0.16-r1.ebuild:
Version bump, modified rc init script thanks to Jasper Bryant-Greene for
reporting a bug
*mysql-5.0.16-r30 (23 Nov 2005)
*mysql-5.0.16 (23 Nov 2005)
23 Nov 2005; Francesco Riosa <vivo@gentoo.org> files/mysql-slot.rc6,
-mysql-4.0.26-r30.ebuild, mysql-4.1.15-r30.ebuild,
-mysql-5.0.13_rc.ebuild, -mysql-5.0.15-r30.ebuild, +mysql-5.0.16.ebuild,
+mysql-5.0.16-r30.ebuild:
Version bump for the 5.0 series.
The ebuild has been rewritten, it's the first step to slot the mysql
database
server. (diff 5.0.16 and 5.0.16-r30 if you don't belive at it)
Also the rc scripts are changed, hopefully bug #109380 is gone (Thanks to
Rodrigo Severo for shaping it).
It's possible from now start more than one server tweaking the
/etc/conf.d/mysql .
The future of slotted MySQL is still uncertain but the rc script will
be kept.
More than uncertain is the slotting of MySQL-4.0 too.
==>reassuming, be careful playing with these ebuilds, never ever
==> "~ARCH" keywords has been so unstable.
-------
Of course, you might want to upgrade to -r2, since clearly some things
didn't work in -r1 (in ebuild terms)
You might also want to stick with stable until things settle down a bit.
Just my 2 Eurocents, as you see, I'm not a MySQL user.
HTH,
Holly
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-24 13:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 14:01 [gentoo-user] How to alter ./configure flags from emerge Harry Putnam
2005-11-23 14:28 ` Alexander Skwar
2005-11-23 15:00 ` [gentoo-user] " Harry Putnam
2005-11-23 15:33 ` Alexander Skwar
2005-11-23 15:52 ` Harry Putnam
2005-11-23 18:20 ` Holly Bostick
2005-11-23 14:55 ` [gentoo-user] " Mattias Merilai
2005-11-23 15:34 ` Alexander Skwar
2005-11-23 16:17 ` Richard Fish
2005-11-24 5:44 ` Alexander Skwar
2005-11-24 10:04 ` Neil Bothwick
2005-11-24 14:11 ` [gentoo-user] " Harry Putnam
2005-11-24 13:44 ` Holly Bostick [this message]
2005-11-24 14:22 ` Neil Bothwick
2005-11-24 16:34 ` Harry Putnam
2005-11-24 16:42 ` Harry Putnam
2005-11-24 15:19 ` Harry Putnam
2005-11-24 14:55 ` Holly Bostick
2005-11-24 15:22 ` Harry Putnam
2005-11-23 18:47 ` Harry Putnam
2005-11-23 15:35 ` Harry Putnam
2005-11-23 16:18 ` Richard Fish
2005-11-23 16:30 ` Richard Fish
2005-11-23 17:56 ` Harry Putnam
2005-11-23 17:31 ` Neil Bothwick
2005-11-23 17:30 ` Harry Putnam
2005-11-23 16:53 ` [gentoo-user] " Francesco R.
2005-11-23 18:37 ` [gentoo-user] " Harry Putnam
2005-11-23 18:10 ` Francesco R.
2005-11-23 18:14 ` [gentoo-user] " Francesco R.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4385C3A5.6050206@planet.nl \
--to=motub@planet.nl \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox