Hi!
> "DownloadFAST" == DownloadFAST com <[EMAIL PROTECTED]> writes:
DownloadFAST> I have not read the MySQL license in detail.
DownloadFAST> Does it allow someone or a group to start another fork of the source that
DownloadFAST> is independent from the current developers?
Yes, you are all
Paul DuBois writes:
> When you distribute a non-GPL application that ONLY works with the MySQL
> server and ships it with MySQL. This type of solution is actually
> considered to be linking even if it's done over a network.
>
> I believe that bit about "even if it's done over the network" was
>
At 7:45 PM + 11/9/01, Carl Troein wrote:
>Shankar Unni writes:
>
>> What are the rules about "bundling" now? If we distribute a (standalone)
>> copy of MySQL with our product, does that expose our product to the GPL? Or
>> is it just like distributing a copy of Emacs with your OS? (I.e. as
%% Shankar Unni <[EMAIL PROTECTED]> writes:
su> Who can answer these questions?
Well, the obvious place to look is the MySQL web site, http://www.mysql.com
Click "Products", then click "MySQL Licensing Policy".
--
-
http://www.mysql.com/doc/G/R/GRANT.html
You need to GRANT 'emdtest.ncr.com' permission to connect or a user from
any box to connect with a user name and password.
mysql> GRANT ALL PRIVILEGES ON *.* TO kenneth@"%"
IDENTIFIED BY 'some_pass' WITH GRANT OPTION;
means kenneth can connect f
Wells, Kenneth L writes:
> I get the error 'Host 'emdtest.ncr.com' is not allowd to connect to this
> MySQL database server'
First of all, I must ask you why you've posted this under a
thread about forking off MySQL. This makes little sense to me.
Secondly, since you just posted the same ques
I get the error 'Host 'emdtest.ncr.com' is not allowd to connect to this
MySQL database server'
How do I correct this???
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.c
r 9, 2001 2:24 PM
To: [EMAIL PROTECTED]
Subject: Re: New fork of MySQL
Steve Meyers wrote:
> The MySQL source is under the GPL. Any fork must also be under the
> GPL. You may sell your forked MySQL, but you must also provide the
> source code.
Is it really, now?
What are the rule
Shankar Unni writes:
> What are the rules about "bundling" now? If we distribute a (standalone)
> copy of MySQL with our product, does that expose our product to the GPL? Or
> is it just like distributing a copy of Emacs with your OS? (I.e. as long as
> you make the source available, it doesn
Steve Meyers wrote:
> The MySQL source is under the GPL. Any fork must also be under the
> GPL. You may sell your forked MySQL, but you must also provide the
> source code.
Is it really, now?
What are the rules about "bundling" now? If we distribute a (standalone)
copy of MySQL with our pro
> >> In fact, I already emailed the developers yesterday, and asked if I
> >> could
> >> pay to have the particular feature I wanted prioritized at this time.
> >
> >Strange how open source developers don't always answer to the almighty
> >dollar, eh?
>
>
>
> I asked kindly that you not turn
I will end my involvement in this thread, because I sense there is too much
noise coming.
If any one with good experience in the MySQL source code base would like to
do some well paid, contracting work for me, please do not hesistate to
email me privately.
Thank you for your consideration of my
>What's so tough
>about making a patch to 3.23 and sending it to the MySQL developers?
3.23 will not the most current cvs soon I assume.
Or does MySQL actively support, debug, fix, and go back and maintain older
releases?
> I
>also doubt that anyone working on the new fork will be able to
Hmm, this has certainly been an interesting discussion. I personally
think that forking the code accomplishes nothing at all. What's so tough
about making a patch to 3.23 and sending it to the MySQL developers? I
also doubt that anyone working on the new fork will be able to convince
thousands
Steve I take your input very constructively and I personally will
definitely reconsider and contemplate more on your point.
In fact, I already emailed the developers yesterday, and asked if I could
pay to have the particular feature I wanted prioritized at this time. And
I don't think that was
On Thu, 2001-11-08 at 23:42, DownloadFAST.com wrote:
>
> Just so you know I am not blowing wind on possible speed enchancement,
> please let me add that one of my former talents was assembler code. Not to
> blow my own horn, but simply to state as fact relevant here, I was able to
> speed up Pai
Just so you know I am not blowing wind on possible speed enchancement,
please let me add that one of my former talents was assembler code. Not to
blow my own horn, but simply to state as fact relevant here, I was able to
speed up Painter's core paint routines by perhaps 30 - 50%. So although
al
Well I would try to leave that up to the people who want to be involved.
But I would say that a good place to start might be here:
http://www.mysql.com/doc/T/O/TODO_future.html
Speeding up the backlog of little things as priority over the major
structural changes, which IMHO are away from MySQL
What specific issues are you focusing on?
DownloadFAST.com wrote:
> More points about proposed wsSQL:
>
> 1. Another point is that any changes in a separate fork can always be
> integrated back into the main fork. Nothing is stopping that. I am just
> proposing some advantages as to why it
More points about proposed wsSQL:
1. Another point is that any changes in a separate fork can always be
integrated back into the main fork. Nothing is stopping that. I am just
proposing some advantages as to why it shouldn't be the minor fork's
responsibility to do that.
2. I would not decide
> I think it would be more useful to work on the main branch and add extra
> value to it, such as Heikki has done. That way all users of MySQL can
> benefit from your fixes, etc.
IMHO I think this would be best too, I know I would like both the
newer/forthcoming features in the 4.x branch, but
[snip]
>The MySQL source is under the GPL. Any fork must also be under the
>GPL. You may sell your forked MySQL, but you must also provide the
>source code.
Thanks. No resistence from me about publishing source.
>Even though I run a small site, I very much like the direction MySQL 4.0
>is
> I have not read the MySQL license in detail.
>
> Does it allow someone or a group to start another fork of the source that
> is independent from the current developers?
>
The MySQL source is under the GPL. Any fork must also be under the
GPL. You may sell your forked MySQL, but you must als
So far, one developer of MySQL has emailed me and said he would help.
I propose we wait to see how many developers are interested, then take a
vote how to structure. If we don't get enough interested developers, then
I guess that means the proposal dies.
I am not interested in being in control.
%% "DownloadFAST.com" <[EMAIL PROTECTED]> writes:
dc> I have not read the MySQL license in detail.
MySQL is under the straight GPL.
--
---
Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools
"Please
I have not read the MySQL license in detail.
Does it allow someone or a group to start another fork of the source that
is independent from the current developers?
If yes, is any one else interested in starting a fork in which the primary
goal would be to improve the smaller todos and performance
26 matches
Mail list logo
