[gentoo-user] How to alter ./configure flags from emerge

[gentoo-user] How to alter ./configure flags from emerge

[Harry Putnam]

I noticed while emerging mysql that the ./configure flags used during
compile contained one that says: --without-docs

Not a good plan for someone knowing zip about mysql.   How can I
change that to --with-docs from cmdline?

Another thing I noticed is this:

 [...] --with-big-tables --without-docs --without-big-tables

What gives with that...?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Alexander Skwar]

Harry Putnam wrote:
> I noticed while emerging mysql that the ./configure flags used during
> compile contained one that says: --without-docs
> 
> Not a good plan for someone knowing zip about mysql.   How can I
> change that to --with-docs from cmdline?

You influence it, by setting USE flags. I'd guess, that "doc"
would be the USE flag you're looking for. So, put something
like

dev-db/mysql	doc

to /etc/portage/package.use:

echo dev-db/mysql doc >> /etc/portage/package.use

Alexander Skwar
-- 
Men of quality are not afraid of women for equality.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Mattias Merilai]

Harry Putnam wrote:

>I noticed while emerging mysql that the ./configure flags used during
>compile contained one that says: --without-docs
>
>Not a good plan for someone knowing zip about mysql.   How can I
>change that to --with-docs from cmdline?
>
>Another thing I noticed is this:
>
> [...] --with-big-tables --without-docs --without-big-tables
>
>What gives with that...?
>
>  
>
I do not know much about mysql, but looking at the latest ebuild it 
seems that it does not look for a doc USE flag. You will have to 
manually change the ebuild to --with-docs. Gentoo's ebuild howto will 
explain you how to do that.
About the --with-big-tables and --without-big-tables, this kind of 
behaviour is usual. There is some logic behind the choice of which 
option will be used, and portage makes use of that. Usually you can 
safely assume portage has already figured that out for you; and in this 
case it checks for the big-tables USE flag to do so.
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Alexander Skwar <listen@alexander.skwar.name> writes:

[...]

> You influence it, by setting USE flags. I'd guess, that "doc"
> would be the USE flag you're looking for. So, put something
> like
>
> dev-db/mysql	doc
>
> to /etc/portage/package.use:
>
> echo dev-db/mysql doc >> /etc/portage/package.use

Just looking at emerge --pretend after setting that I'm confused by
the output:

emerge -v -u -p mysql: (wrapped for mail)
These are the packages that I would merge, in order:

 Calculating dependencies  ...done!
[ebuild  N    ] dev-db/mysql-5.0.15  +berkdb -big-tables 
 -cluster -debug -doc -extraengine -minimal +perl +readline
 (-selinux) +ssl -static -utf8 0 kB 

Note that doc has the - sign and readline has +, shouldn't doc have
come up without minus.  

Then when I actually run the emerge the compile flags are not altered
one whit, notice in the actual command given the compiler, the next 
to last line shows `--without-docs'.  But also there appears a 
--without-readline (8th line down) when emerge told me in the
`pretend' run `+readline'.

This is getting pretty confusing

./configure --prefix=/usr --host=i686-pc-linux-gnu 
  --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share 
  --sysconfdir=/etc --localstatedir=/var/lib --libexecdir=/usr/sbin 
  --sysconfdir=/etc/mysql --localstatedir=/var/lib/mysql
  --with-low-memory  --enable-assembler --enable-local-infile 
  --with-mysqld-user=mysql --with-client-ldflags=-lstdc++ 
  --enable-thread-safe-client --with-comment=Gentoo Linux mysql-5.0.15 
  --with-unix-socket-path=/var/run/mysqld/mysqld.sock 
  --with-zlib-dir=/usr --with-lib-ccflags=-fPIC --without-readline 
  --enable-shared --enable-static --without-libwrap --with-openssl 
  --without-debug --with-bench --with-server --with-embedded-server 
  --with-extra-tools --with-innodb --with-raid --with-extra-charsets=all 
  --with-berkeley-db=./bdb --with-geometry --without-ndbcluster 
  --with-big-tables --without-docs --without-big-tables 
  --build=i686-pc-linux-gnu
 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Alexander Skwar]

Harry Putnam wrote:
> Alexander Skwar <listen@alexander.skwar.name> writes:
> 
> [...]
> 
>> You influence it, by setting USE flags. I'd guess, that "doc"
>> would be the USE flag you're looking for. So, put something
>> like
>>
>> dev-db/mysql	doc
>>
>> to /etc/portage/package.use:
>>
>> echo dev-db/mysql doc >> /etc/portage/package.use
> 
> Just looking at emerge --pretend after setting that I'm confused by
> the output:

Me too. Seems that the system didn't get that change.
Please send output of:

grep dev-db/mysql /etc/portage/package.use

> Note that doc has the - sign and readline has +, shouldn't doc have
> come up without minus.  

Yes.

> 
> Then when I actually run the emerge the compile flags are not altered
> one whit,

Of course not. Wouldn't have expected.

Alexander Skwar
-- 
Men of quality are not afraid of women for equality.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Alexander Skwar]

Mattias Merilai wrote:

> I do not know much about mysql, but looking at the latest ebuild it 
> seems that it does not look for a doc USE flag.

I disagree. Check the output of "emerge -pv dev-db/mysql".

Alexander Skwar
-- 
Men of quality are not afraid of women for equality.
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Mattias Merilai <jah@ut.ee> writes:

> seems that it does not look for a doc USE flag. You will have to
> manually change the ebuild to --with-docs. Gentoo's ebuild howto will
> explain you how to do that.

And this can be found....where?  I've been jerking around on
gentoo.org for over 1/2 hr now and haven't spotted it in the lists of
documentation with the search features on Firefox since gentoo.org has
not even a search engine for its own pages.

Nearest I've come is:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#book_part2_chap3

   You are advised to edit the ebuild's src_compile() function if you
   want to change the compilation instructions. However, you can also
   trick Portage into believing that the ebuild application has finished
   the compile steps. Run all necessary commands yourself and create an
   empty file called .compiled in the working directory:

I might get it right from this but is there more explicit coverage
somewhere?

I'm not asking you to dig up a URL just something off the top of your
head to guide my own search.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Alexander Skwar <listen@alexander.skwar.name> writes:


> Me too. Seems that the system didn't get that change.
> Please send output of:
>
> grep dev-db/mysql /etc/portage/package.use

dev-db/mysql mysql mysqli
dev-db/mysql doc
dev-db/mysql ndb-doc



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Richard Fish]

On 11/23/05, Alexander Skwar <listen@alexander.skwar.name> wrote:
> I disagree. Check the output of "emerge -pv dev-db/mysql".

No, look at the ebuilds in portage:

The mysql builds currently available are:

mysql-3.23.58-r1.ebuild
mysql-4.0.25-r2.ebuild
mysql-4.0.26.ebuild
mysql-4.1.14.ebuild
mysql-4.1.15-r30.ebuild
mysql-4.1.15.ebuild
mysql-5.0.15.ebuild
mysql-5.0.16-r30.ebuild
mysql-5.0.16.ebuild


The mysql builds that USE doc are:
mysql-4.0.25-r2.ebuild
mysql-4.0.26.ebuild
mysql-4.1.14.ebuild
mysql-4.1.15.ebuild
mysql-5.0.15.ebuild

So, Harry, which version of mysql are you trying to merge?

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Richard Fish]

On 11/23/05, Harry Putnam <reader@newsguy.com> wrote:
> And this can be found....where?

/usr/portage/profiles/use*.desc

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Richard Fish]

On 11/23/05, Richard Fish <bigfish@asmallpond.org> wrote:
> On 11/23/05, Harry Putnam <reader@newsguy.com> wrote:
> > And this can be found....where?
>
> /usr/portage/profiles/use*.desc

Oops, sorry, thought you were asking about where to find the USE flag.
 I was reading out-of-order...and not thinking right.

The full devguide is at:

http://dev.gentoo.org/~plasmaroo/devmanual/

Assuming you really need a specific version of mysql, and do not want
to merge a version that already has the doc USE flag, the general idea
is that you will want to:

1. Copy /usr/portage/dev-db/mysql to your PORTDIR_OVERLAY directory,
being sure to keep the directory structure intact.
2. Edit PORTDIR_OVERLAY/dev-db/mysql/mysql-<version>.ebuild.  Modify
the configure steps as you want.
3. Run ebuild mysql-<version>.ebuild digest
4. Merge mysql as normal.

You can probably do some cleanup of the files in PORTDIR_OVERLAY to
remove everything not related to the version of mysql that you want.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Francesco R.]

Alle 15:01, mercoledì 23 novembre 2005, Harry Putnam el ga butta:
> |I noticed while emerging mysql that the ./configure flags used
> | during compile contained one that says: --without-docs
> |
> |Not a good plan for someone knowing zip about mysql.   How can I
> |change that to --with-docs from cmdline?
> |
> |Another thing I noticed is this:
> |
> | [...] --with-big-tables --without-docs --without-big-tables
> |
> |What gives with that...?

That's a bug in the ebuild, the next one will fix this. As a mitigating 
factor the rightmost option override the left ones.
In the ebuild the rightmost is set by use flags.

readline:
the use flag has always worked in "inversed" mode, but it's too late to 
discuss about it, it will be removed in the next ebuilds (always 
linking to the system readline)

also the "configure" option you see at compile time may _not_ be the 
same the ebuild used, _but_ what the ebuild set always override the 
MySQL default.

just in case you are thnking to play with mysql-5.0.16 wait for 
dev-db/mysql-5.0.16-r2 <-- r2 but be advised that it's shiny new 
and ... buggy.

Cheers,
Francesco R.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Richard Fish <bigfish@asmallpond.org> writes:

> /usr/portage/profiles/use*.desc

Those are a HOWTO about creating ebuilds?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On Wed, 23 Nov 2005 11:56:43 -0600, Harry Putnam wrote:

> I don't need a specific version I simply want the docs to be built.
> Adding a use flag of doc or docs does not cause it to be built.  At
> least not in what was current portage day before yesterday.

That's because your/etc/portage/package.use file is messed up. You can
only have one entry for a package, otherwise the previous entries are
overridden by the last one.

An alternative, when a ./configure option is not covered by USE flags is
to put in in the EXTRA_ECONF variable, although this won't work with
every ebuild.

EXTRA_ECONF="--enable-blah" emerge foo/bar


-- 
Neil Bothwick

If at first you don't suceed, try the switch marked "Power"

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Richard Fish <bigfish@asmallpond.org> writes:


> Assuming you really need a specific version of mysql, and do not want
> to merge a version that already has the doc USE flag, the general idea
> is that you will want to:

I don't need a specific version I simply want the docs to be built.
Adding a use flag of doc or docs does not cause it to be built.  At
least not in what was current portage day before yesterday.

Right now I've run sync and see there is a newer ebuild that does now
show anyting about doc on a pretend install... I'm not sure what that
means but soon as an `emerge -v -u world' finishes I'm going to watch
the install of it and see what is really passed to the compiler.


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Francesco R.]

Alle 19:37, mercoledì 23 novembre 2005, Harry Putnam el ga butta:
> |"Francesco R." <vivo@gentoo.org> writes:
> |
> |
> |[...] Snipped good info here  ...  Thanks
> |
> |> also the "configure" option you see at compile time may _not_ be
> |> the same the ebuild used, _but_ what the ebuild set always
> |> override the MySQL default.
> |
> |So we cannot really tell what is passed to the compiler?  The output
> |of emerge is just nonsense compared to what really happens?

The output of emerge _is_ what really happens, as it's the output from 
the build system (auto* tools and gcc)
Consider the first "configure" you find:

------------
/var/tmp/portage/mysql-5.0.16-r2/work/mysql
>>> Source unpacked.
 * before to use federated engine be sure to read
 * http://dev.mysql.com/doc/mysql/en/federated-limitations.html
 * econf: updating mysql/bdb/dist/config.guess 
with /usr/share/gnuconfig/config.guess
 * econf: updating mysql/bdb/dist/config.sub 
with /usr/share/gnuconfig/config.sub
 * econf: updating mysql/config.guess 
with /usr/share/gnuconfig/config.guess
 * econf: updating mysql/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu 
--mandir=/usr/share/man [......] --without-big-tables 
--build=i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
------------

for example "--build=i686-pc-linux-gnu" it's not directly setted by the 
ebuild (speaking of ebuild code, not the portage one)

and this other (sub)configure, it also contain option not setted by the 
ebuild.

---------------
config.status: executing default commands
configure: configuring in innobase
configure: running /bin/sh './configure' --prefix=/usr  
'--prefix=/usr' [......] --cache-file=/dev/null --srcdir=.
checking build system type... i686-pc-linux-gnu
---------------

As a final ans side note, it's gentoo policy that the ebuild set all the 
configure options avaiable to it (but it's not _mandated_ to leave the 
user the possibility to select them via use-flags).


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Francesco R.]

Alle 15:01, mercoledì 23 novembre 2005, Harry Putnam el ga butta:
> |I noticed while emerging mysql that the ./configure flags used
> | during compile contained one that says: --without-docs
> |
> |Not a good plan for someone knowing zip about mysql.   How can I
> |change that to --with-docs from cmdline?
> |
> |Another thing I noticed is this:
> |
> | [...] --with-big-tables --without-docs --without-big-tables
> |
> |What gives with that...?

/me damn stupid, I've forgot to mention that readding the documentation 
from MySQL is planned in a short term.
It has been splitted out from the source distribuited .tar.gz about 
at ?4.1.12?

:P

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Holly Bostick]

Harry Putnam schreef:
> Alexander Skwar <listen@alexander.skwar.name> writes:
> 
> 
> 
>> Me too. Seems that the system didn't get that change. Please send
>> output of:
>> 
>> grep dev-db/mysql /etc/portage/package.use
> 
> 
> dev-db/mysql mysql mysqli dev-db/mysql doc dev-db/mysql ndb-doc
> 
> 
> 
Harry, put all the USE flags on one line. What is happening to you is
that the lines do not concantate (add on to each other, however you
spell that word), they override each other.

The way you have it, first the mysql and mysqli flags are being turned
on, then the flags go back to default, and the doc flag is turned on,
then the flags go back to default and the ndb-doc flag is turned on, so
ndb-doc is the only non-default flag that ultimately is turned on.

But if you have

dev-db/mysql mysql mysqli doc ndb-doc

(just one line instead of three), they will all be turned on.

I usually find it helpful to pop into package.use with nano and do a
Ctrl-W search to confirm that I have not already set some USE flags for
a popular application (if I modify it a lot), so I know whether to add
to an existing line or create a new one. Since I'm already in nano,
creating a new line if necessary is easy enough.

Hope this helps,.
Holly


-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

"Francesco R." <vivo@gentoo.org> writes:


[...] Snipped good info here  ...  Thanks

> also the "configure" option you see at compile time may _not_ be the 
> same the ebuild used, _but_ what the ebuild set always override the 
> MySQL default.

So we cannot really tell what is passed to the compiler?  The output
of emerge is just nonsense compared to what really happens?

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Alexander Skwar <listen@alexander.skwar.name> writes:

> Mattias Merilai wrote:
>
>> I do not know much about mysql, but looking at the latest ebuild it 
>> seems that it does not look for a doc USE flag.
>
> I disagree. Check the output of "emerge -pv dev-db/mysql".

The original output I posted:
 Calculating dependencies  ...done!
[ebuild  N    ] dev-db/mysql-5.0.15  +berkdb -big-tables 
 -cluster -debug -doc -extraengine -minimal +perl +readline
 (-selinux) +ssl -static -utf8 0 kB 

After an emerge sync I get different output:
=======================
Calculating dependencies ...done!
[ebuild  N    ] dev-db/mysql-5.0.16-r1  +berkdb -big-tables -cluster
  -debug -extraengine -minimal +perl (-selinux) +ssl -static -utf8 18,650 kB 

I used the sync because my fumbling attempts to edit the ebuild I had
in there caused emerge to error out about the recorded size of ebuild.

Its been replaced now and as you see the ouput is different.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Alexander Skwar]

Richard Fish schrieb:
> On 11/23/05, Alexander Skwar <listen@alexander.skwar.name> wrote:
>> I disagree. Check the output of "emerge -pv dev-db/mysql".
> 
> No, look at the ebuilds in portage:
> 
> The mysql builds currently available are:
[...]
> mysql-4.1.15.ebuild
> mysql-5.0.15.ebuild
> mysql-5.0.16-r30.ebuild
> mysql-5.0.16.ebuild
> 
> 
> The mysql builds that USE doc are:
[...]
> mysql-5.0.15.ebuild
> 
> So, Harry, which version of mysql are you trying to merge?

5.0.15.

emerge -v -u -p mysql: (wrapped for mail)
These are the packages that I would merge, in order:

 Calculating dependencies  ...done!
[ebuild  N    ] dev-db/mysql-5.0.15  +berkdb -big-tables
 -cluster -debug -doc -extraengine -minimal +perl +readline
 (-selinux) +ssl -static -utf8 0 kB

As I said: I disagree :)

But I was "shocked" to see that in post-5.0.15, the
doc USE flag was removded. So, talking about the
current ebuilds, you're right.

Alexander Skwar
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to alter ./configure flags from emerge

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 393 bytes --]

On Thu, 24 Nov 2005 06:44:51 +0100, Alexander Skwar wrote:

> But I was "shocked" to see that in post-5.0.15, the
> doc USE flag was removded.

Aren't they being moved to a separate build? This makes a lot of sense,
there are times you need the docs but not the programs on your computer.


-- 
Neil Bothwick

WinErr 003: Dynamic linking error - Your mistake is now in every file

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Holly Bostick]

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

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Alexander Skwar <listen@alexander.skwar.name> writes:

> Richard Fish schrieb:
>> On 11/23/05, Alexander Skwar <listen@alexander.skwar.name> wrote:
>>> I disagree. Check the output of "emerge -pv dev-db/mysql".
>> 
>> No, look at the ebuilds in portage:
>> 
>> The mysql builds currently available are:
> [...]
>> mysql-4.1.15.ebuild
>> mysql-5.0.15.ebuild
>> mysql-5.0.16-r30.ebuild
>> mysql-5.0.16.ebuild

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.

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


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...

Anyone here who has perused mysql.com will know it is a difficult task
to find basic information there.

You can get error messages in 12 of the worlds languages but can't
find out how to get a basic setup running.

Someone said the docs were a separate package but `esearch' doesn't
turn up any in the present portage.    

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Thu, 24 Nov 2005 14:44:05 +0100, Holly Bostick wrote:

> Are there in fact docs available for this version yet? From MYSQL, I
> mean, not Gentoo.

Yes, in various formats from http://dev.mysql.com/doc/.

> Except that most of those flags are no longer valid for the unstable
> version...
> 
> ACCEPT_KEYWORDS="~x86" emerge -pv mysql

I thought you were trying not to set variables on the command line :)
 
> > 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...

There was a note at the end of the emerge:

 * You might want to run:
 * "emerge --config =dev-db/mysql-5.0.16-r2"
 * if this is a new install.

did you do this?


-- 
Neil Bothwick

Is it possible to be totally partial?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: How to alter ./configure flags from emerge

[Holly Bostick]

Harry Putnam schreef:
> Holly Bostick <motub@planet.nl> writes:
> 
>> 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.
>> 
> Holly, Thanks for the usual helpful effort.  Maybe you can tell me 
> how one controlls what ebuild is used.  For example:
<snip>
> I was able to to at least start mysql-5.0.15.ebuild, how would I 
> select it out of the others thru emerge?

Lots of ways-- to return to the stable build, try

# echo 'dev-db/mysql x86' >>/etc/portage/package.keywords

This will essentially change the ACCEPT_KEYWORDS setting for this
package only to stable. You may also have to add settings for the
dependencies, as they will still be unstable versions if you do not, and
I don't know how well the stable mysql build plays with the unstable
versions of its dependencies.

To only allow version 5.0.15, try

# echo '>dev-db/mysql-5.0.15' >>/etc/portage/package.mask

This will mask all unstable versions above 5.0.15. You will have to be
responsible for unmasking later versions when you feel that they have
stabilized to your needs (meaning, you have to keep an eye on the status
of the ebuilds, because even when later versions go stable, you won't
have them available to you in Portage).

So I would almost say go back to stable, and when the currently unstable
upgrades become stable, just upgrade normally. Unless you have some
burning reason to have version 5 now, today, no matter what the
circumstances.
> 
> 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....


Ummmm.... no you don't so much need to use the actual path as you need
to use the correct syntax to emerge a particular version of a package:

emerge =dev-db/mysql-5.0.15

or emerge (<=>)[= - the exact version; >= - any version greater than or
equal to; <= - any version less than or equal to; > - any version
greater than; < - any version less than]cate-gory/package-version.number

Naturally if you do something like this, though, you'll want to utilize
package.mask to block other versions so that Portage doesn't try to
upgrade or downgrade the package you've specifically emerged in a
particular version.


HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

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

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Harry Putnam <reader@newsguy.com> writes:

>
> Anyone here who has perused mysql.com will know it is a difficult task
> to find basic information there.

This was something of a boneheaded undertaking at mysql.com.
Somewhere I got that address as the source of docs etc.  For any other
interested party who is dumb as me you should look at:

      www.mysql.org   <= note the `org' not com

Where you will find piles of beginner docs.

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Neil Bothwick <neil@digimed.co.uk> writes:


[...]

> There was a note at the end of the emerge:
>
>  * You might want to run:
>  * "emerge --config =dev-db/mysql-5.0.16-r2"
>  * if this is a new install.
>
> did you do this?

(First I've backed of 5.16 since I couldn't even start it from:
  /etc/init.d/mysql
Unemerged and reemerged 5.15)

Gack, no, I missed that completely.

So backing up here I ran that and it errors out because apparently a
db was actually built in all my tinkering so rm -rf /var/lib/mysql

(in the current case 5.0.15
And rerun emerge --config =dev-db/mysql-5.0.15

It now works and queries for a password which I gave it.  There were a
large pile of warning about being `Unable to load' /usr/share/zoninfo
stuff <Snipped in the output below>

I don't understand the warnings about supplying a password since the
first step is to do that.... trying the suggested commands:
  /usr/bin/mysqladmin -u root password 'new-password'
  /usr/bin/mysqladmin -u root -h reader password 'new-password'
Fail like this
 /usr/bin/mysqladmin -u root password 'hpreader'
 error: 'Access denied for user 'root'@'localhost' (using password: NO)'

Whats this all about?

OUTPUT of emerge --config =dev-db/mysql-5.0.15

See the manual for more instructions.
emerge --config =dev-db/mysql-5.0.15
========================================
Configuring pkg...

 * MySQL DATADIR is /var/lib/mysql
 * Creating the mysql database and setting proper
 * permissions on it...
 * Insert a password for the mysql 'root' user
 * Avoid ["'\_%] characters in the password
    >
 * Check the password
    >
Installing all prepared tables
Fill help tables

To start mysqld at boot time you have to copy support-files/mysql.server
to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h reader password 'new-password'
See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory:
cd sql-bench ; perl run-all-tests

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com

[...] snipped warnings leaving only one sample:
Warning: Unable to load '//usr/share/zoneinfo/Asia/Riyadh87' as time zone. Skipping it.
[...]
. * Loading "zoneinfo" this step may require few seconds
 * done
==========================================================






-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to alter ./configure flags from emerge

[Harry Putnam]

Neil Bothwick <neil@digimed.co.uk> writes:

> Yes, in various formats from http://dev.mysql.com/doc/.

Thanks... have you noticed under the most promising heading:
  Post-Installation Setup and Testing
there are only directions for windows or specific `unix' users?

And that the linux directions revolve strictly around rpm installation
for further help one is refered back to explicit windows or `unix'
directions. 



-- 
gentoo-user@gentoo.org mailing list