public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthew Marlowe" <mattm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Re: [gentoo-dev] Creating a dedicated gentoo profile for commercial mysql support
Date: Fri, 22 Apr 2005 21:09:17 -0700	[thread overview]
Message-ID: <20050423040818.5298AF5944@mail.deploylinux.net> (raw)


>> Matthew Marlowe wrote:
>> <too big snip because I'm writing in vncviever>
>> - there are tests that show mysql compiled with icc much faster,
>> obviously only on intel box
>> - you can find a very basic ebuild for mysql-bin at b.g.o/83424
>> - packages for mysql-4.1 have been dowloaded hundreds times starting
>> 2004-12 from b.g.o/83011 and http://www.francesco-riosa.com/gentoo/
>>   very few reported bugs, mostly ebuild related (not mysql fault)
>> - the story is totally different if you look at mysql-5.0 or gcc-4.0
>> currently there are 74 Mb of compile/test log that can document it.
>> - on the server maillist the idea of a slow update / hyper stable branch
>> has been not very well accepted as far as I can remember.
>> 

If we were just talking about a single mysql 4.1 server sure, the gentoo
ebuilds have been great.  I haven't had any problem with it and the mysql
ebuild writers have been very good.

Unfortunately, my clients would like to use mysql 5 (which will released from
beta to production in June/July according to the conference), clusters (which
can get complicated), best possible performance, and commercial support.  

That seems to point towards getting a stable profile, icc, and binaries at the moment.

As far as the stable branch, I've heard alot of devs really like the idea - and several
want to contribute to it, but there just wasnt enough momentum and there were
technical issues involved (such as keeping copies of distfiles around for long
periods).

>> LIFO proposal
>> 
>> - Learn from TV, update your server in "differita" <- translate as
>> needed.  Follow the updates of the main stable branch ... delayed 4 weeks.
>>  You will have a 100 times more tested tree than the hyper stable one.
>> We need a handly way to do this
>> - Apart from the icc compiled ones avoid the use of precompiled binary.
>>   MySQL compiling and running depends from few other things:
>>   = linux-headers  / kernel ?
>>   = glibc
>>   = gcc / compiler
>>   = crypt
>>   = ssh
>>   = readline
>>   = perl
>>   = nsl
>>   = tcp wrappers
>> Ask to MySQL ab what version of theese they certify and build in loco
>> the stuff should be non plus ultra
>> 

Thanks for the list above.  I'll definitly pay attention to all these items.

>> Best regards
>> Francesco Riosa
>> 

Regards,
Matt

>> --
>> gentoo-dev@gentoo.org mailing list
>> 
>> 
>> 


-- 
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2005-04-23  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23  4:09 Matthew Marlowe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-23  4:01 Re: [gentoo-dev] Creating a dedicated gentoo profile for commercial mysql support Matthew Marlowe

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=20050423040818.5298AF5944@mail.deploylinux.net \
    --to=mattm@gentoo.org \
    --cc=gentoo-dev@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