public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Rodgers <steve.rodgers@ts-a.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mysql commercial
Date: Tue, 3 Jan 2006 18:51:42 +0000	[thread overview]
Message-ID: <200601031851.42725.steve.rodgers@ts-a.com> (raw)
In-Reply-To: <43BAC420.5050009@gentoo.org>

so unless it's of real use to others I might just continue to support it myself.
I'm already packaging up other internal apps using a portage overlay.

FYI - if you deploy an app which is non-gpl which links against mysql libs then
you need to deploy against a commercial version of mysql.
this is built and maintained in binary format by mysql - and requires 
username/password to download.

there are various packages - rpms and tarballs available.

for commercial apps using the mysql c api you must use commercial mysql - if you
use e.g. php then that's ok as there is a php clause in the license.

Steve

On Tuesday 03 Jan 2006 18:36, Francesco Riosa wrote:
FR> Jakub Moc wrote:
FR> [...]
FR> > Dunno what exactly "commercial" means here, it you mean official -bin,
FR> > there's some overlay and ebuilds in Bug 83424, there's also some weird
FR> [...]
FR> 
FR> Please forget that one, it's broken, and the quantity and the size of
FR> the binary packages to download make an hell to maintain it, i.e.
FR> (unless you want to maintain just x86 and amd64 ARCHs)
FR> 
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-01-03 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 17:54 [gentoo-dev] mysql commercial Steve Rodgers
2006-01-03 18:21 ` Francesco Riosa
2006-01-03 18:25 ` Jakub Moc
2006-01-03 18:36   ` Francesco Riosa
2006-01-03 18:51     ` Steve Rodgers [this message]
2006-01-03 18:53       ` Steve Rodgers

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=200601031851.42725.steve.rodgers@ts-a.com \
    --to=steve.rodgers@ts-a.com \
    --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