From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to alter ./configure flags from emerge
Date: Thu, 24 Nov 2005 09:19:26 -0600 [thread overview]
Message-ID: <87mzju9ipt.fsf@newsguy.com> (raw)
In-Reply-To: 4385C3A5.6050206@planet.nl
Holly Bostick <motub@planet.nl> writes:
[...] good info
> 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.
Holly,
Thanks for the usual helpful effort. Maybe you can tell me how one
controlls what ebuild is used. For example:
ls /usr/portage/dev-db/mysql
ChangeLog mysql-4.0.25-r2.ebuild mysql-5.0.15.ebuild
Manifest mysql-4.0.26.ebuild mysql-5.0.16-r1.ebuild
files mysql-4.1.14.ebuild mysql-5.0.16-r30.ebuild
metadata.xml mysql-4.1.15-r30.ebuild
mysql-3.23.58-r1.ebuild mysql-4.1.15.ebuild
I was able to to at least start mysql-5.0.15.ebuild, how would I
select it out of the others thru emerge?
I foolishly ran the last -u world with ACCEPT_KEYWORDS=~x86 and have
since set that globally. So I'm now bleeding edge and it appears that
it would take some doing to undo that at this point so thought I'd go
with it for a while and see if I could get ontop of it.
I know about using the actual path and that is how I'm installing it
as I write but one always gets those troublesome messages about
installing by path being broken....
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-24 14:33 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
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 [this message]
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=87mzju9ipt.fsf@newsguy.com \
--to=reader@newsguy.com \
--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