02.03.2016 16:16, Egor Pugin wrote:
> What about just 'firebird'? 'core' is misleading.
> It does not matter that the same word repeats in address. See:
> https://github.com/git/git
> https://github.com/FFmpeg/FFmpeg
> https://github.com/openssl/openssl
> and many others...
Let's look at closer e
2016. 02. 24. 13:20 keltezéssel, Norbert Saint Georges írta:
> ok, sorry I did not understand.
>
> I found the source of a new VM and it compiles under lazarus 3.0 good
> :-)
Hi Norbert,
How did you do it?
I tried with FPC 3.0.0 without success. In original state with "fpc
Firebird.pas" command
Gabor Boros a écrit :
> 2016. 02. 24. 13:20 keltezéssel, Norbert Saint Georges írta:
>> ok, sorry I did not understand.
>>
>> I found the source of a new VM and it compiles under lazarus 3.0 good
>>> -)
>
> Hi Norbert,
>
> How did you do it?
>
> I tried with FPC 3.0.0 without success. In original
Em 13/03/2016 07:22, Dmitry Yemanov escreveu:
>
> If the latter, then I agree that we should better replace "core" with
> either "firebird" or "server".
>
With "server" I disagree, as our core code is not only server.
Adriano
-
2016. 03. 13. 14:48 keltezéssel, Norbert Saint Georges írta:
> Hi Gabor
> Delphi (-Delphi)
> It is magic :-)
How simple solution. :D Thank you!
Tried Adriano's example and (after small modifications) works like a charm.
Gabor
-
Hello, All.
Should be allowed to use non-local path in alias expansion? I.e.
local_database=remote_server:real_database
If yes, alias expansion belongs to Y-valve, if not - to the engine.
--
WBR, SD.
--
Tr
> How should the docs and QA be located?
As I understand 'qa' in svn is a directory, not a project. Github does
not support hierarchical structure. In 'qa' dir there are some repos:
'benchmark', 'fbtest', 'fbt-repository' etc.
So, you'll have:
https://github.com/firebirdsql/firebird
https://github
On 13-3-2016 17:10, Egor Pugin wrote:
> Jaybird repos will be prefixed as you wrote.
> https://github.com/firebirdsql/jaybird
> https://github.com/firebirdsql/jaybird-manual
>
> It's an option to move Jaybird to its own account. So you won't mix
> repos with same names.
> https://github.com/jaybird
+1
13 марта 2016 г. 7:15 PM пользователь "Mark Rotteveel"
написал:
> On 13-3-2016 17:10, Egor Pugin wrote:
> > Jaybird repos will be prefixed as you wrote.
> > https://github.com/firebirdsql/jaybird
> > https://github.com/firebirdsql/jaybird-manual
> >
> > It's an option to move Jaybird to its ow
13.03.2016 17:36, Adriano dos Santos Fernandes wrote:
>
>> If the latter, then I agree that we should better replace "core" with
>> either "firebird" or "server".
>
> With "server" I disagree, as our core code is not only server.
Well, I'm pretty sure mariadb/server includes also the client librar
13.03.2016 19:10, Egor Pugin wrote:
>
> As I understand 'qa' in svn is a directory, not a project. Github does
> not support hierarchical structure. In 'qa' dir there are some repos:
> 'benchmark', 'fbtest', 'fbt-repository' etc.
> So, you'll have:
> https://github.com/firebirdsql/firebird
> https:
> qa-fbtest ... firebird-qa-fbtest
Both looks good. If you're planning to have other 'qa' projects like
'jaybird-qa*' second is better.
Finally, you can rename repositories very easy anytime.
On 13 March 2016 at 23:16, Dmitry Yemanov wrote:
> 13.03.2016 19:10, Egor Pugin wrote:
>>
>> As I unders
Might this be a good time to restructure the code into separate
projects, maybe:
* Engine
* Remote interface
* Y-valve
* Server (exclusive of Y-valve and engine, etc)
* Utilities
* Common code
Splitting the code base would strengthen the underlaying architecture,
spotlight unnecessary de
13 matches
Mail list logo
