Home Zeos 7 Failing to install
Reply: 1

Zeos 7 Failing to install

Mark Patterson
1#
Mark Patterson Published in 2012-11-28 11:23:06Z

I have installed the Zeos 7 Beta on my own machine but it fails on my client's laptop. We're both running Delphi xe2, his is Entreprise, mine is Pro. His machine is running 64-bit windows 7, mine is running Window 7 32-bit.

When I do Compile all on ZeosDbo or ProjectGoup16 it seems to get through ZCore.dpk but then shows 2 fatal errors:

ZCore.dpk(1) E2225 Never-build package 'ZCore' must be recompiled 
ZParseSQL.dpk(33) E2202 Required package 'ZCore' not found 

This is production code we are working on, so I hope we can find a solution and get back to working on this

Zeos forum thread: http://zeos.firmos.at/viewtopic.php?t=3633

Arioch 'The
2#
Arioch 'The Reply to 2012-11-28 13:13:28Z

That is one error, the 1st one. The second is merely post-effect. Perhaps you can do better than downloading beta ZIPs: until they have mature release you just can download each day "nightly" changes by version-control tools, like Git or SVN or whatever Zeos team is using. Such errors are usually quickly fixed (they are simple) but long released(they are so moot that no one would bother making release for them).

Just open http://zeos.firmos.at/portal.php and read where to get most instant updates and how to report problems.

Actually - there it is, http://svn.code.sf.net/p/zeoslib/code-0/trunk/ Install TortoiseSVN and be on the edge until 7.0.1 or 7.0.2 final release

The page also says: Please report bugs for this version to our brand new bugtracker on sourceforge https://sourceforge.net/p/zeoslib/tickets/ Please do. Open Source is about participating. At least participate by registering bugs.

About the essence of problem read official documentation and "See Also" section. Someone should decide about package binary update strategy. And the decision should be kept for all packages (okay, you can mix it in some conditions, but that is not to be suggested). So basically you have three choices:

  1. Make your own decision and put all Zeos packages into the strategy of your choice. That puts the responsibility upon yourself to maintain this fork for a while until you come back to vanilla ZeosDB.

  2. Report the bug to ZeosDB team and ask their suggestion, then change those settings for all the packages as suggested by them.

  3. Report the bug to ZeosDB team and wait until they'd fix it in their SVN and then do SVN Update.

    • Personally i'd go with 1 option, but i am ready to be FLOSS libraries co-developer.
    • Option 3 would be the most slow yet the most easy for you.
    • Option 2... well... i can not see why you should choose that, except for trying to avoid version controls at any cost, which is bad idea per se.

I also suggest you to read http://www.catb.org/esr/faqs/smart-questions.html
That would help you effectively communicate at ZeosDB forums - and you'd have to if you want to be "on the edge" (and if you do not - then wait for public release like 7.0.2).

You need to login account before you can post.

About| Privacy statement| Terms of Service| Advertising| Contact us| Help| Sitemap|
Processed in 0.369075 second(s) , Gzip On .

© 2016 Powered by mzan.com design MATCHINFO