public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francesco Riosa <francesco@pnpitalia.it>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] mysql-bin ebuild
Date: Thu, 24 Feb 2005 12:57:59 +0100	[thread overview]
Message-ID: <421DC147.20100@pnpitalia.it> (raw)
In-Reply-To: <20050222171919.GB22112@curie-int.vc.shawcable.net>

Robin H. Johnson ha scritto:

>On Tue, Feb 22, 2005 at 01:55:57PM +0100, Francesco Riosa wrote:
>  
>
>>After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to 
>>me that is very difficult have a stable version of those databases with 
>>current glibc, gcc and maybe os-headers stable defaults (at least on x86 
>>and amd64).
>>
>>Adding a dev-db/mysql-bin package seems the only short-term viable 
>>solution to have those versions of mysql in portage tree. Leaving out 
>>all the problems that dependant packages have after mysql 4.1.3 release.
>>
>>I'm going to writing an ebuild that (maybe using alternatives.eclass) 
>>unpack the binary distribuited version of mysql in /opt/ dir and symlink 
>>all the programs to paths currently used from the source dist.
>>
>>any input on how to write it in a way that permit it to be included in 
>>the portage tree very apreciated, expecially that from Robin H. Johnson 
>>a.k.a robbat2
>>    
>>
>I'd say it should be mutually exclusive of the source-built version
>(DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
>instead of messing around with symlinks. However I think it should use
>the same /var/lib/mysql for it's data directory.
>  
>
Ok, I'll discover how to add a /etc/env.d/98mysql

>By default it should provide the stock binaries, if USE=max, then
>provide the mysql-max binaries, and if USE=debug, instead provide the
>debugging binaries.
>
>  
>
IUSE="max debug innodb berkdb selinux utf8 perl ruby"

with "max" and "debug" mutually exlusive,
"innodb" "berkdb" "selinux" "utf8"  modifying  the my.cnf file
"perl" "ruby" operating on RDEPEND
?

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-02-24 11:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 12:55 [gentoo-dev] mysql-bin ebuild Francesco Riosa
2005-02-22 17:19 ` Robin H. Johnson
2005-02-24 11:57   ` Francesco Riosa [this message]
2005-02-24 19:36   ` Donnie Berkholz
2005-02-25  9:18     ` Francesco Riosa
2005-02-25 10:13       ` [gentoo-dev] -* v.s. package.mask Georgi Georgiev
2005-02-25 10:45         ` Francesco Riosa
2005-02-25 13:16         ` Ciaran McCreesh
2005-02-25 13:18         ` Chris Gianelloni
2005-02-25 11:40       ` [gentoo-dev] mysql-bin ebuild Martin Holzhauer
2005-02-25 12:44         ` Francesco Riosa
2005-02-27  1:26   ` Francesco Riosa
2005-02-22 18:46 ` Stuart Herbert
2005-02-22 19:28   ` Francesco Riosa
2005-02-22 20:11     ` Jeff Smelser
2005-02-23  2:20   ` Francesco Riosa
2005-02-22 19:03 ` Jeff Smelser
2005-02-22 19:35   ` Francesco Riosa
2005-02-22 20:17     ` Jeff Smelser
2005-02-22 20:26       ` Francesco Riosa
2005-02-24 14:40         ` Jeff Smelser
2005-02-24 15:12           ` Francesco Riosa
2005-02-24 15:12             ` Francesco Riosa
2005-02-24 15:28             ` Jeff Smelser

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=421DC147.20100@pnpitalia.it \
    --to=francesco@pnpitalia.it \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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